It looks like after catching the DEE a HardDEError is probably thrown
which causes the server instance to quit and the next request will
cause a new instance to be spun up.
I had to give up catching DEE's - you don't get enough time to
reliably start a new task. The only option seems to be to start your
clean up code after 25 seconds for example.
The other "request aborted..." errors are due to your app restarting
and taking too long. The request that kills the server instance is
followed by other requests that will time out after 10 seconds if you
app has not finished reloading.
So two things to work on: 1) clean up task before DEE thrown 2) speed
up app loading time
John
On 6 Jun 2010, at 21:19, Felipe Quintella Correia wrote:
Hello,
I hope someone can help me. Even though this is not a critical
problem, it's really annoying me. Every time i catch a
DeadlineExceededException and I try to patch things up and end my
thread properly I get a
(Error code 104). I already tried searching everywhere, tried ending
the thread immediately, throwing another exception, yadda yadda... But
I always end up with this error after my logs. The clean up is
properly done, meaning I get what I should (new tasks in queue to
continue the process and the logs I made while cleaning up). I really
have no idea what to do.
Log:
#06-05 10:21PM 33.811 /canalparser?main=updateShows&tasknumber=29 200
33423ms 4487cpu_ms 2135api_cpu_ms 0kb AppEngine-Google;
(+http://code.google.com/appengine)
See details
0.1.0.2 - - [05/Jun/2010:22:22:07 -0700] "GET
/canalparser?main=updateShows&tasknumber=29 HTTP/1.1" 200 0
"http://tvguidebr.appspot.com/canalparser?main=scheduleShowsUpdate";
"AppEngine-Google; (+http://code.google.com/appengine)"
"tvguidebr.appspot.com"
I 06-05 10:21PM 38.099
braziltvguide.ParseCanaisServlet doGet: Starting thread
I 06-05 10:21PM 38.289
braziltvguide.ParseCanaisServlet updateShows: Updating Shows for
E! Entertainment (29 of 112)
W 06-05 10:22PM 07.079
braziltvguide.ParseCanaisServlet updateShows: Deadline Detected
- Ending Thread
I 06-05 10:22PM 07.079
braziltvguide.ParseCanaisServlet doGet: Ending thread - Timer:
28980ms
W 06-05 10:22PM 07.215
A serious 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)
Another error I get in a frequent basis, but I don't know if they are
related is:
06-05 10:21PM 43.823
Request was aborted after waiting too long to attempt to service your
request. This may happen sporadically when the App Engine serving
cluster is under unexpectedly high or uneven load. If you see this
message frequently, please contact the App Engine team.
The task eventually gets done after retrying a certain number of times
(usually 1 but all the way up to 5 or 6).
Thank you in advance,
Felipe Quintella
--
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
.
--
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.
