On 13 Jan 2010, at 14:43, Wesley Chun (Google) wrote:
john, HardDeadlineExceededError cannot be caught. you should see DeadlineExceededException and catch that instead...
I am not catching HDEE - I am catching DEE and then starting a new task to continue the original tasks work
as explained in this thread below, seeing HardDeadlineExceededError means that something has caused DeadlineExceededException to get discarded or
as above - it is not being discarded. The problem is that occasionally I am not given enough time after catching it to "clean up". However, normally I am.
it's going so fast, that there wasn't any time to throw DeadlineExceededException: http://groups.google.com/group/google-appengine-java/browse_thread/thread/409f3c244c10674f/2978dcb88890e8a9 what kinds of operations is your app performing, and do they seem to take longer than 30 secs?
Yes I push the task to do as much work in 30 secs, catch the "times up" exception and start a new task. As I said, this was working reliably but now fails occasionally.
My question was actually about the stack trace. Because it appears to be coming from where the DEE was thrown and not in my clean up code.
-- 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.
