That's correct--the task still completes successfully even after the timeout exception shows up in the console window.
Vince On Fri, Dec 4, 2009 at 5:11 PM, Max Ross (Google) <maxr+appeng...@google.com<maxr%2bappeng...@google.com> > wrote: > We're using the UrlFetchService to invoke the task URL, and the local > implementation of UrlFetchService times out after 5 seconds. For task > execution the timeout should instead be 30 seconds. I'll get a fix > together, but in practice the timeout shouldn't actually impact the > completion of the task. UrlFetchService will timeout but the task should > still finish running. > > Thanks, > Max > > > On Fri, Dec 4, 2009 at 7:06 AM, Vince Bonfanti <vbonfa...@gmail.com>wrote: > >> Hi Max, >> >> Yes, it works. Thanks very much. >> >> Vince >> >> P.S. While step-debugging a task, I noticed that they seem to time-out >> very quickly--within about 5 seconds. Is this intentional? Here's a partial >> stacktrace: >> >> Dec 4, 2009 3:03:58 PM >> com.google.appengine.api.labs.taskqueue.dev.DevQueue runTask >> SEVERE: Exception executing task 24b5a6e4-c327-4bc6-bc4f-51f838f3d1a5 on >> queue write-behind-task >> com.google.apphosting.api.ApiProxy$ApplicationException: ApplicationError: >> 5: http method GET against URL >> http://127.0.0.1:8080/_ah/queue/write-behind-task?watchdog=839445f1-2c77-4c2c-bf32-81b88d5e092etimed >> 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 >> com.google.appengine.api.labs.taskqueue.dev.DevQueue.runTask(DevQueue.java:221) >> at >> com.google.appengine.api.labs.taskqueue.dev.LocalTaskQueue.runTask(LocalTaskQueue.java:313) >> >> On Thu, Dec 3, 2009 at 7:01 PM, Max Ross (Google) < >> maxr+appeng...@google.com <maxr%2bappeng...@google.com>> wrote: >> >>> Vince, >>> >>> We added a last minute fix for this in the SDK that just went out. Could >>> you please try your code with the official SDK download? >>> >>> Thanks, >>> Max >>> >>> >>> On Thu, Dec 3, 2009 at 12:15 PM, Max Ross (Google) < >>> maxr+appeng...@google.com <maxr%2bappeng...@google.com>> wrote: >>> >>>> Sure, sorry for the trouble, and thanks for trying out the prerelease! >>>> >>>> Max >>>> >>>> >>>> On Thu, Dec 3, 2009 at 12:12 PM, Vince Bonfanti <vbonfa...@gmail.com>wrote: >>>> >>>>> That fixed it. Thanks. >>>>> >>>>> Vince >>>>> >>>>> >>>>> On Thu, Dec 3, 2009 at 2:24 PM, Max Ross (Google) < >>>>> maxr+appeng...@google.com <maxr%2bappeng...@google.com>> wrote: >>>>> >>>>>> Vince, >>>>>> >>>>>> As a workaround, try setting the missing environment attribute >>>>>> explicitly before you add the task to the queue: >>>>>> >>>>>> ApiProxy.getCurrentEnvironment().getAttributes().put("com.google.appengine.server_url_key", >>>>>> "http://localhost:8080";); >>>>>> >>>>>> This should only be necessary for tasks that are added when there is >>>>>> no "live" request and it should have no impact in prod. >>>>>> >>>>>> Sorry for the trouble, >>>>>> Max >>>>>> >>>>>> >>>>>> On Thu, Dec 3, 2009 at 10:20 AM, Max Ross (Google) < >>>>>> maxr+appeng...@google.com <maxr%2bappeng...@google.com>> wrote: >>>>>> >>>>>>> Hi Vince, >>>>>>> >>>>>>> That sounds like a bug in our code that was a side effect of the >>>>>>> automatic task execution that now happens in the dev environment. Let >>>>>>> me >>>>>>> see if I can come up with a workaround for you. >>>>>>> >>>>>>> Max >>>>>>> >>>>>>> On Thu, Dec 3, 2009 at 10:06 AM, Vince Bonfanti <vbonfa...@gmail.com >>>>>>> > wrote: >>>>>>> >>>>>>>> I just started testing with the 1.2.8 prerelease, and I'm getting >>>>>>>> the following exception from Queue.add() in code that works in 1.2.6: >>>>>>>> >>>>>>>> java.lang.IllegalStateException: Current enviornment must have the >>>>>>>> server url available via the com.google.appengine.server_url_key >>>>>>>> attribute. >>>>>>>> >>>>>>>> This only happens when Queue.add() is invoked from the servlet >>>>>>>> init() method or from a static initializer; if Queue.add() is invoked >>>>>>>> from a >>>>>>>> "regular" request thread, then it works properly. >>>>>>>> >>>>>>>> Vince >>>>>>>> >>>>>>>> -- 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 google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
