Yep, we're rolling this out slowly with the 1.3.3 release to let developers know that some requests are slow because they are startup requests.
On Wed, Apr 21, 2010 at 6:09 AM, Tristan <[email protected]>wrote: > Hey, > > I started seeing when a task queue starts now: > > WARNING: 200 OK > This request caused a new process to be started for your application, > and thus caused your application code to be loaded for the first time. > This request may thus take longer and use more CPU than a typical > request for your application. > > instead of this > > WARNING: 500 > Request was aborted after waiting too long to attempt to service your > request. Most likely, this indicates that you have reached your > simultaneous dynamic request limit. This is almost always due to > excessively high latency in your app. Please see > http://code.google.com/appengine/docs/quotas.html for more details. > > I like it. Is this the expected behavior from now on? > > Tristan > > -- > 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]<google-appengine-java%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > -- Ikai Lan Developer Relations, Google App Engine Twitter: http://twitter.com/ikai Delicious: http://delicious.com/ikailan ---------------- Google App Engine links: Blog: http://googleappengine.blogspot.com Twitter: http://twitter.com/app_engine Reddit: http://www.reddit.com/r/appengine -- 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.
