Folks, I had some evidence last year ( http://paulhammant.com/blog/appengines-blind-spot.html ) that it was a second app-engine instance being started from my app and not the first instance being taken down, and a new one started up.
Specifically, it seemed to me that second and subsequent app-engine instances were started in advance of the first instance being loaded. This is still a form of "cold starts", but not quite as some are thinking. Having tried the same app today, I can't see the issue I saw for launch of GAE/J. There are still issues in that I have a problem with the way it handles session scoped objects, but the main issue is not there anymore. At least it is not for a rudimentary test. If anyone wants the source for the app to make a private instance for more measured and private testing, it's linked to from the blog entry above. - Paul -- 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
