You can read quite a lot about this here: https://developers.google.com/appengine/articles/deadlineexceedederrors
The short answer is that if you have a request which gets deadline exceeded, that request is handled (fairly) gracefully by having the exception bubble up. All other requests on the same instance are killed, and you get the message you saw for each of those requests. The instance is killed too. My guess is this is the only way to ensure that an instance doesn't overconsume resources in a multi-tenant environment. If you check your logs, you should be able to see the cause of this, you just need to look at the logs that don't contain this message and see why they're dying. Usually this is a SearchService, Datastore or URLFetch issue. On Friday, December 13, 2013 7:08:56 AM UTC+11, Hans Jakobsen wrote: > > Since 3 hours ago, all requests to our appengine application fails with > this message in the log: > > A problem was encountered with the process that handled this request, causing > it to exit. This is likely to cause a new process to be used for the next > request to your application. If you see this message frequently, you may be > throwing exceptions during the initialization of your application. (Error > code 104) > > > > Nothing was changed in our source code on either sides. Google please > solve this and in the future do not beta test on real users !!! > > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
