I'd like to be sure that there is no loss from overriding _ah_warmup. The documentation is rather ambiguous on this point: "[<warmup-requests-enabled>... defaults to true ... causes the App Engine infrastructure to issue GET requests to /_ah/warmup, initializing <load-on-startup><http://code.google.com/appengine/docs/java/config/appconfig.html#Using_a_load-on-startup_Servlet>servlets, ServletContextListeners<http://code.google.com/appengine/docs/java/config/appconfig.html#Using_a_ServletContextListener>, and custom servlets<http://code.google.com/appengine/docs/java/config/appconfig.html#Using_a_Custom_Servlet>—which allow you to initialize your application's code as it requires." I'll admit it seems reasonable to interpret the statement to mean that all the initialization will take place in addition to running the Servlet#servicemethod of a Servlet named _ah_warmup. It would be nice if it were clear that _ah_warmup's service method is the last thing in the initialization sequence before directing user requests to the instance.
I've tried a few tests and I'm not sure if I'm getting a warmup when going from one instance to 2 instances. At any rate, my filter is not seeing a Request for /_ah/warmup. -- 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.
