I find it interesting that Glassfish will return 503 error (Service Unavailable) and will show informative message while it is busy loading the application. Then user knows that he(or she) needs to reload the page in browser, and the app will come up.
I guess from free service we can't ask that application will be always on hot standby, loaded in memory and ready to go. But then again, 30seconds appengine cold startup for a Rails appliation stack (JRuby and Rails3.0pre) is just killing. I wonder if it's just particularly bad today... but on my testing app, it seems that ever other request times out (is killed by the 30 seconds HardDeadlineExceededError) as app stack is trying to spin itself up. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
