RC6.7 Error deploying to Jelastic cloud

AFter I have migrated my project to RC6.7 and converted customer datatypes. It works locally but couldn’t finish deployment in Jelastic Cloud with the followoing exceptions:

[CubaJelasticDeploy] uploading progress: [80%]
[CubaJelasticDeploy] uploading progress: [90%]
[CubaJelasticDeploy] uploading progress: [100%]
:jelasticDeployWar FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':jelasticDeployWar'.
> [CubaJelasticDeploy] upload failed: max size = 157286400

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.


Total time: 14 mins 10.189 secs
[20:36:08.679] Task 'jelasticDeployWar' failed
java.lang.RuntimeException: [CubaJelasticDeploy] upload failed: max size = 157286400

Thanks for your suggestion or confirmation of bug.

Hi CUBA team
May I have some help here?

It seems the generated WAR file is too big.
As written here, the maximum file size for uploading is 150MB but you can still deploy it:

  1. Execute the jelasticBuildWar task.
  2. Find app.war in the /build/distributions/war folder.
  3. Host it somewhere.
  4. Define the URL on the URL tab.


Hi Rostislav
Thanks. It worked. Is did it as follows:

  1. Go to Mirhost. Select Upload - URL. Entered FTP URL as follows

    Then deploy…

Now question is:
In case i upload from ftp connection, is there any mechanism that can be used to update the database?


I found later after deployment that the database is updated. Thanks for your help.

Do you mean automatic DB update?

When you deploy a project to Cloud using Studio, two Gradle tasks are executed:

  1. jelasticBuildWar. As result of this task execution, app.war appears in the /build/distributions/war folder.
  2. jelasticDeployWar. This task just uploads the WAR to Jelastic. And it is automatically deployed afterward.

Database is updated during the application start if the cuba.automaticDatabaseUpdate is enabled. The property is written to app.properties which is packed to the generated WAR. So automatic DB-update does not depend on the way how the file is delivered to Cloud.


Thank you.