If this is the issue, you might find that AWS or Azure meets your needs better. It seems that GAE, as of now, is more tuned for simpler web sites and not for more complex processing.
I suspect that there might be a workaround where, around the 25 second mark, reinvoke the URL with some state information to resume the work. Another alternative is to figure out how to quantize your work, then have a local server app invoke the right URLs as needed. I know that this is suboptimal, but if you are committed to using GAE, it might be needed. The local server can be pretty low end if it is just invoking URLs. -----Original Message----- From: google-appengine@googlegroups.com [mailto:google-appeng...@googlegroups.com] On Behalf Of J Keller Sent: Wednesday, June 03, 2009 4:09 PM To: Google App Engine Subject: [google-appengine] Re: DeadlineExceededException - how to avoid? That might help some, but according to the docs: A cron job will invoke a URL at a given time of day. A URL invoked by cron is subject to the same limits and quotas as a normal HTTP request, including the request time limit. Unfortuantely, I don't think I can reasonably break my task down into (20 or fewer) small enough pieces to not exceed that time limit. I'll keep investigating other approaches, thanks Scott. -J On Jun 3, 11:17 am, "Scott Seely" <sc...@scottseely.com> wrote: > You have access to cron jobs which can handle long running work. Seehttp://code.google.com/appengine/docs/java/config/cron.htmlfor java,http://code.google.com/appengine/docs/python/config/cron.htmlfor python. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
