I got this error a quarter of an hour ago. My app presented me with the, in my view, unprofessional error 500 page (see my feature request to change this at http://code.google.com/p/googleappengine/issues/detail?id=4674).
When a new instance of my app is created, an initialisation task is enqueued for immediate execution. Both the original browser and the enqueued task client web requests failed and generated the log warning entries you describe below. I request that the severity of this type of log entry be changed from warning to error; it's not just a warning since a user has been unable to access the site and got the GAE error 500 page instead. Also, I echo Tarun's question: what is the cause of the problem? Can I work around this? Ian Marshall On Mar 7, 9:19 am, tarun2000 <[email protected]> wrote: > I keep getting: 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. (Error code 202) > > It seems like the issue happens right after uploading a new version or on > cold start. It seems to disappear after a while. The rpcs that fail may > be returning a lot of data. Any idea what's wrong? -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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?hl=en.
