GAE for Java picking wrong / old jars

[Daniel Florey]

I am seing this issue once in a while:

I'm uploading a new version of my app including updated jars, but GAE still uses old versions of the jars.

Anybody else?

[Patrice (Cloud Platform Support)]

Hi Daniel!

What do you mean by "once in a while"? How frequent is this? Do you have any way to reliably reproduce that issue? We'd be happy to look into it, but we'd need some clear reproduction steps. Once you have that, I would suggest opening this on the issue tracker as a defect report, with enough information to reliably reproduce. We do monitor that site as well, so no worries for that :).

Cheers!

[Emanuele Ziglioli]

Could it simply be some instances with old versions of your code still being active?

[Daniel Florey]

Hi Patrice,

thanks for the reply.

I've opened an issue on the issue tracker.

https://code.google.com/p/googleappengine/issues/detail?id=12035

If someone from Google want to dig into this I could provide access to one of my apps where I encounter this issue.

Thanks,

Daniel

[Jeff Schnitzer]

Assuming you are using maven, the most likely solution is 'mvn clean' and rebuild. It appears that maven (or the gae maven plugin) sometimes does not remove old jars so you end up with multiple jars in the deployment. At that point it's pretty random which one actually gets loaded.

Jeff

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-appengi...@googlegroups.com.
To post to this group, send email to google-a...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/0e2b3cf3-fd38-41db-acfd-fe484456996a%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Jeff Schnitzer]

I should point out that I haven't experienced this myself. I only know about it because very rarely I get a support request on the objectify list for a stacktrace generated by an old version of objectify (shortly after they upgrade). 'mvn clean' solves it.

Jeff