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 wrote:
> I just updated from 1.
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)"
wrote:
> Local task execution is using the local UrlFetchService implementation with
> its def
sorry I should have been more precise, essentially I am concerned
about blowing the 30sec per request processing/duration limit
previously I was bulk uploading csv files and parsing them into POJOs
then persisting them via JDO to pre-populate my app data ...
I was encountering both the 5sec DS op
I am also facing simmilar problem. Any clue?
--
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-appengi
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.
Regarding the "per-request quota"
Are you worried about the number of requests or the duration of those
requests?
On Mon, Dec 7, 2009 at 11:17 AM, Larry Cable wrote:
> Hi Max, after sleeping on it, it became apparent that as you describe
> the timeout is
> in fact in the "client" and not th
Your approach sounds fine. As an alternative you could schedule the next
task up front, then check to see if there is any work to be done, then
proceed. That way you'll always have the next task scheduled no matter what
might go wrong during processing.
On Mon, Dec 7, 2009 at 2:19 PM, Larry Cabl
Please re-read the thread leading up to your post. The timeout shouldn't
impact the completion of the request on the server. If you're seeing
something different please let me know.
Thanks,
Max
On Thu, Dec 10, 2009 at 10:26 PM, Heyali wrote:
> I am also facing simmilar problem. Any clue?
>
>
