Re: Re-deployment on appengine sometimes breaks GWT app (Module.Cache.html not found)
Yes, changing the version is the best way. GAE seems to fail its uploads fairly regularly in my experience. Just use a build number along with your version, upload, smoke test to verify it is working, and then mark as current version in the GAE console. -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: Re-deployment on appengine sometimes breaks GWT app (Module.Cache.html not found)
Today it happened again. - It definitely is NOT the browser cache. - I redeployed various times, without success. - From the appengine console I deleted the active instance without success. Then finally I incremented the version (appengine-web-app.xml), redeployed and switched the versions manually in the appengine console. - Does one have to change the version to ensure a successful switch? -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: Re-deployment on appengine sometimes breaks GWT app (Module.Cache.html not found)
On 09.04.13 10:15, Jens wrote: Never used AppEngine but the first two things I would check are: 1.) Caching issue for module.nocache.js so that the browser has the old one cached and requests an old .cache.html file which does not exist anymore. I wish - I cleared the cache and tried different browsers to no avail. 2.) Maybe AppEngine distributes your app across different nodes which may take a while and you hit a node that is not updated yet (load balancing issue). Yes that was my thought too, it looks like an appengine issue, but how do you 'prove' that? - it's so spurious. -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: Re-deployment on appengine sometimes breaks GWT app (Module.Cache.html not found)
Never used AppEngine but the first two things I would check are: 1.) Caching issue for module.nocache.js so that the browser has the old one cached and requests an old .cache.html file which does not exist anymore. 2.) Maybe AppEngine distributes your app across different nodes which may take a while and you hit a node that is not updated yet (load balancing issue). -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re-deployment on appengine sometimes breaks GWT app (Module.Cache.html not found)
Hi, Every now and then when uploading an update of my GWT application to appengine, the uploaded app seems in an inconsistent state, i.e. the Module.Cache.html file is not found. e.g. App not working, Browser console says '/Module/C96DE337B74EEDDBD2CF70FC4C65827B.cache.html not found' This is scary, since I never know if an update will break my site. Workaround: Typically, if I deploy again immediately, it will work. But meanwhile the site is not working. Has anyone every had this problem? Any ideas as to what could go wrong? Many thanks -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
