Error deploying project in google appengine

S

sonriente2011-09-07 15:06:22

Java

sonriente, 2011-09-07 15:06:22

Hello.

When trying to deploy a project to google appengine, the error "Found a jar file too large to upload" occurs when trying to upload appengine-api-1.0-sdk-1.5.3.jar (15.8 mb with a limit of 10 mb per file)
The problem is already known since 2009, a lot of tickets in the google issue tracker, but there are only two suggestions on the Internet how to fix this:

1) Either add the --enable_jar_splitting option. Naturally I tried that.
For some reason it doesn't work. I tried with different versions of the SDK (1.4.3, 1.5.2 and the latest 1.5.3 were at hand) - no success. 2) Unpack appengine-api-1.0-sdk-1.5.3.jar to WEB-INF/lib. Here another problem arises: Google's limitation is 3000 files per project. Appengine-api-1.0-sdk-1.5.3.jar has about 3500 files + about 50 of mine. 3) I thought of the 3rd method myself - you can delete the archive from WEB-INF / lib. Works for simple projects. In the case of projects that use the full power of the app engine, the hint will not work (i.e. I need to use the datastore. Without appengine-api-1.0-sdk-1.5.3.jar, the project deploys, but does not work. In the Google console, of course, mistakes)

appengine-java-sdk-1.5.3/bin/appcfg.sh -e [email protected] --enable_jar_splitting update project/war Reading application configuration data... ...... java.lang.IllegalStateException: Found a jar file too large to upload: "/tmp/appcfg4869648953084473935.tmp/WEB-INF/classes/war/WEB-INF/lib/appengine-api-1.0-sdk-1.5.3.jar". Consider using --enable_jar_splitting. Unable to update app: Found a jar file too large to upload: "/tmp/appcfg4869648953084473935.tmp/WEB-INF/classes/war/WEB-INF/lib/appengine-api-1.0-sdk-1.5.3.jar". Consider using --enable_jar_splitting. Please see the logs [/tmp/appcfg5857347513630341491.log] for further information.

Wrote on google. No answer, no hello.
Please tell me how to solve this problem. I must have missed something somewhere.

Reply

Answer the question

In order to leave comments, you need to log in

1 answer(s)

S

sonriente, 2011-09-07
@sonriente

Everything ingenious is simple. I found workaround myself. Hope it helps someone. Although it would be cool if Google itself finally scratched itself and fixed the problem.
#du -sh appengine-api-1.0-sdk-1.5.3.jar
18M appengine-api-1.0-sdk-1.5.3.jar
#jar -xf appengine-api-1.0-sdk-1.5.3.jar
#jar -cf appengine-api-1.0-sdk-1.5.3-repacked.jar com/ javax/ META-INF/ org/
#du -sh appengine-api-1.0-sdk-1.5.3-repacked.jar
6.1M appengine- api-1.0-sdk-1.5.3-repacked.jar