In my case it's throwing a DeadlineExceededError before it even reaches the code responsible for handling the request, meaning there are no service requests at all before the error, only imports. It occurs mostly when starting a new instance of the application so yes, it's related to the imports taking too long. But importing Django 1.1 shouldn't take 30 seconds (that's the time for every request with DeadlineExceededError).
On Sep 22, 5:41 pm, Geoffrey Spear <geoffsp...@gmail.com> wrote: > On Sep 22, 10:25 am, Fredrik Bonander > > <carl.fredrik.bonan...@gmail.com> wrote: > > Yes. But I can't see how this is relevant since (at least for me) the error > > always occur during datastore calls (at least for me) > > If the requests it's happened on are always loading requests (they'll > have an INFO-level logging message to that effect), it's likely > because your framework is taking a long time to import everything, > giving you less time to do datastore calls after the imports. If > they're not just on loading requests, maybe you're trying to squeeze > too many (or too large) datastore calls into a request. -- 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-appeng...@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.
