Wednesday, June 25, 2014

Re: GWT RemoteServiceServlet serialization policy

Yes I guess this would be a lead.. I have a load balancer (apache) in front of the servlet container..
Looking at the caching headers it says Cache-Control max-age=0

I am looking for a way to test if this is it.. any ideas?

On Wednesday, June 25, 2014 4:48:44 PM UTC+3, Jens wrote:
However the client still gets IncompatibleRemoteServiceException although the response gets to the client (which has the new code base) but it fails to be deserialized.
So, even after refresh of the page, the users get that exception. And all the users that access that module will get that exception for a while.

Any ideas? 

I guess something is caching your old app.nocache.js file which will load old <permutation>.cache.html files (that are also cached). Maybe a web proxy? Make sure your app.nocache.js file has correct HTTP caching headers. You don't want that file to be cached at all costs.

-- J.

You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To post to this group, send email to
Visit this group at
For more options, visit

No comments:

Post a Comment