I am paying for 3 reserved server instances and have a Spring based web app that isn’t doing anything fancy, initializing about 15 beans at startup. My logs show that the app can be initialized in less than 3 seconds and consumes around 4 seconds of cpu time on successful warm ups.
However the warm up can take much longer. Particularly over the last 3 days I’ve noticed that roughly 1/3 of the time the warm up fails with a DeadlineExceeededException sometime after 30 seconds. I was also surprised to find that sometimes the warmup was successful, but took around 40 seconds. (I thought GAE would always timeout the request after 30 seconds.) I’m curious if anyone else is experiencing this and if the GAE team has an explanation for this behavior. -- 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-java@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.
