Hi Max, after sleeping on it, it became apparent that as you describe the timeout is in fact in the "client" and not the execution of the (servlet) task itself ... On Dec 7, 10:54 am, "Max Ross (Google)" <[email protected]> wrote: > Local task execution is using the local UrlFetchService implementation with > its default timeout: 5 seconds. So, if the url that your task hits takes > more than 5 seconds to respond you'll see this exception. However, this > exception is from the client of the task url, not the task execution > itself. The client will timeout after 5 seconds but the task should still > execute to completion - we don't interrupt it. Please let me know if that's > not the case.
so I concur with your assertion above ... > > Now, 5 seconds is clearly not enough time since the request limit for apps > is 30 seconds. This is a bug, and it's already fixed. It should go out > with the next SDK. In the meantime just try to ignore the timeouts. great thanks ... Since I am using GAE-VFS and tasks in order to upload, parse and persist data via JDO into the DataStore, I anticipate that the Servlet/Task will potentially exceed the per-request quota and throw ... I was planning on catching this and scheduling additional tasks until all the file processing is complete ... any thoughts on this ... do you see any problems in doing so? > > As for retries, this is a known > limitation:http://code.google.com/appengine/docs/java/taskqueue/overview.html#Ta... > > We'll get this brought in line with production shortly. > > Thanks, and sorry for the trouble. > no problem! ... Thanks for the response! > Max > > > > On Sun, Dec 6, 2009 at 9:57 PM, Tristan <[email protected]> wrote: > > I've seen this as well. I've also noticed that if I purposefully make > > a task fail (by returning any HTTP status code outside of the range > > 200-299), it doesn't get added back to queue for retrying. This used > > to work in 1.2.6. > > > -Tristan > > > On Dec 6, 4:18 pm, Larry Cable <[email protected]> wrote: > > > I just updated from 1.2.6 to 1.2.8 and my application code has started > > > failing locally. > > > > I am using task queue's in order to process uploaded files, this > > > worked in 1.2.6 (although you had > > > to manually fire the task queue from the _ah admin console) > > > > Now, it is failing under 1.2.8 (as it seems as though it is now > > > automatically starting the queue) > > > with the following exception: > > > > Dec 7, 2009 12:08:57 AM org.quartz.core.JobRunShell run > > > SEVERE: Job default.a7f0abc6-ed81-4fa4-96f1-c09048a99883 threw an > > > unhandled Exception: > > > com.google.apphosting.api.ApiProxy$ApplicationException: > > > ApplicationError: 5: http method POST against > > URLhttp://localhost:8080/admin/gae-tasks/upload/csv/irs/processor.task > > > timed out. > > > at > > com.google.appengine.api.urlfetch.dev.LocalURLFetchService.fetch > > > (LocalURLFetchService.java:214) > > > at > > com.google.appengine.api.labs.taskqueue.dev.UrlFetchJob.execute > > > (UrlFetchJob.java:53) > > > at > > com.google.appengine.api.labs.taskqueue.dev.UrlFetchJob.execute > > > (UrlFetchJob.java:46) > > > at org.quartz.core.JobRunShell.run(JobRunShell.java:195) > > > at org.quartz.simpl.SimpleThreadPool$WorkerThread.run > > > (SimpleThreadPool.java:520) > > > Dec 7, 2009 12:08:57 AM org.quartz.core.ErrorLogger schedulerError > > > SEVERE: Job (default.a7f0abc6-ed81-4fa4-96f1-c09048a99883 threw an > > > exception. > > > org.quartz.SchedulerException: Job threw an unhandled exception. [See > > > nested exception: com.google.apphosting.api.ApiProxy > > > $ApplicationException: ApplicationError: 5: http method POST against > > > URLhttp://localhost:8080/admin/gae-tasks/upload/csv/irs/processor.task > > > timed out.] > > > at org.quartz.core.JobRunShell.run(JobRunShell.java:206) > > > at org.quartz.simpl.SimpleThreadPool$WorkerThread.run > > > (SimpleThreadPool.java:520) > > > * Nested Exception (Underlying Cause) --------------- > > > com.google.apphosting.api.ApiProxy$ApplicationException: > > > ApplicationError: 5: http method POST against > > URLhttp://localhost:8080/admin/gae-tasks/upload/csv/irs/processor.task > > > timed out. > > > at > > com.google.appengine.api.urlfetch.dev.LocalURLFetchService.fetch > > > (LocalURLFetchService.java:214) > > > at > > com.google.appengine.api.labs.taskqueue.dev.UrlFetchJob.execute > > > (UrlFetchJob.java:53) > > > at > > com.google.appengine.api.labs.taskqueue.dev.UrlFetchJob.execute > > > (UrlFetchJob.java:46) > > > at org.quartz.core.JobRunShell.run(JobRunShell.java:195) > > > at org.quartz.simpl.SimpleThreadPool$WorkerThread.run > > > (SimpleThreadPool.java:520) > > > > it implies that there is some form of timeout occuring ... since the > > > app code has not changed and is not > > > apparently getting invoked at all, I am somewhat at loss to know how > > > to resolve this! > > > > Has anyone else seen these problems? > > > -- > > > 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]<google-appengine-java%2b[email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/google-appengine-java?hl=en.- Hide quoted > >text - > > - Show quoted text - -- 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.
