JMIX 1.x app NOT working on AWS - Communication error: Invalid JSON from server: 1|X

[tomas.klems (Tomáš Klemš)]

I managed to fix (hotfix) the issue using the massive timeouts as suggested by

JMIX 1.x app NOT working on AWS - Communication error: Invalid JSON from server: 1|X

So I also had this problem and I also did a lot of investigation and trial and error. For the application load balancer I use a HTTP client keep alive duration: 3600 seconds. Very long I know. Somehow it seems to help. Also a Connection idle timeout: 900 seconds. For the nginx proxy configuration I use the following: proxy_connect_timeout 600s; proxy_read_timeout 900s; proxy_send_timeout 900s; proxy_set_header Connection $connecti…

I have never seen this error since this.

FYI, For AWS EB, the change of nginx config is lost after restart/redeploy/…
To make it permanent, use AWS EB .platfom extension.

For EB deployment, make a zip, which will contain

• uber jar
• .platform/nginx/conf.d/elasticbeanstalk/timeout.conf

with this content: timeout.conf

    proxy_connect_timeout    600s;
    proxy_read_timeout    900s;
    proxy_send_timeout   900s;

It is also good idea to create a Gradle task to reate that zip.

build.gradle:

...
.....
.......
tasks.register('createPlatformDir', Copy) {
    into('build/.platform')
    from('src/main/elasticbeanstalk/.platform')
}
tasks.register('createEbExtensionsDir', Copy) {
    into('build/.ebextensions')
    from('src/main/elasticbeanstalk/.ebextensions')
}

tasks.register('bundleForElasticBeanstalk', Zip) {
    dependsOn bootJar
    dependsOn createPlatformDir
    dependsOn createEbExtensionsDir
    from('build/libs') {
        include '*.jar'
    }
    into('.platform') {
        from('build/.platform')
    }
    into('.ebextensions') {
        from('build/.ebextensions')
    }
    archiveBaseName.set("aws-eb-${project.name}")
    destinationDirectory.set(file('build/distributions'))
}

Good luck!