Thanks for the link, Stephen. In my case, the code do get executed, they fail on datastore put(), mostly due to DEE, timeout, ApplicationError. In normal circumstances, the failure is rare and it gets caught by catch blocks, nicely. However, sometimes during a short time frame, there are sudden bursts of this kind of errors, and when that happens, the catch blocks never get a chance to run, according to our logs.
Best, Will On Tue, Mar 8, 2011 at 8:13 PM, Stephen <sdeasey+gro...@gmail.com> wrote: > On Tue, Mar 8, 2011 at 11:10 AM, Will <vocalster....@gmail.com> wrote: > > Thanks for the suggestion, Robert. > > > > The problem is, under normal conditions, the catch blocks do get > > executed. I've seen ApplicationError, db.Timeout and even > > DeadlineExceededError get caught. But during this kind of error > > spikes, I don't see the same piece of code get a chance to run. > > > Try this: > > > http://code.google.com/appengine/docs/python/config/appconfig.html#Custom_Error_Responses > > specifically, the 'timeout' error handler. > > Your exception handler wont run if none of your code is run if, for > example, there was a timeout in the google infrastructure before an > instance could be allocated to run your code. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
