That's not the request timeout; when you get that message your request never started being processed at all because the system was unable/ unwilling to spawn a new instance for you and the existing ones were still busy.
On Apr 2, 4:10 pm, James <[email protected]> wrote: > ... except that sometimes it's 10 seconds ... > > http://code.google.com/p/googleappengine/issues/detail?id=2396 > > On Apr 2, 5:45 am, djidjadji <[email protected]> wrote: > > > The 30 sec limit is still in operation for all the requests: browser, > > cron and task queue > > > 2010/4/2 conman <[email protected]>:> I searched the > > docs but didn't find something about the request > > > timout. > > > > The last time I read something about (around Feb 09) it it was at max. > > > 30 sec per request. > > > > Does this limitation still exist? I mean with the introduction of cron > > > jobs inside GAE this limitation should have been dropped... or are the > > > cron jobs intended to be of very high granularity? > > > > If it's the case that requests can run as long as they want, how can > > > one abort requests that are hang up (for example due to a programming > > > mistake)? > > > > Cheers, > > > Constantin > > > > -- > > > You received this message because you are subscribed to the Google Groups > > > "Google App Engine" 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 > > > athttp://groups.google.com/group/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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?hl=en.
