I think our app was running into this issue also. We are using our own django and parts of the appengine helper patch. I would see 500 errors, deadlineexceeded but the exception is thrown in the django, helper or pyamf (in our case we use pyamf to process the requests from a flex/flash client) code which was even before any datastore operations or much else ran.
The question is. How do you set it up so that django/helper are cached imports? If you import things in main.py (where our main method is) does that keep things in memory? The docs seem to be pretty light on details about how to do this. -Mike On Feb 8, 3:19 am, conman <constantin.christm...@googlemail.com> wrote: > Davel63, are you also using appengine patch? > > On 8 Feb., 04:48, Devel63 <danstic...@gmail.com> wrote: > > > We see the same thing, and just converted to Django. Sounds like it > > may be related to Django. > > > On Feb 7, 11:09 am, johnP <j...@thinkwave.com> wrote: > > > > No solution - just gathering information. Looking more closely at the > > > logs where the errors occur, the deadline exceeded pops up somewhere > > > while loading and patching django. This started a couple days ago. > > > Maybe it'll go away? > > > > Oh well - I'm gonna enjoy the rest of the weekend, and will come back > > > to this on Monday. :) > > > > johnP > > > > On Feb 7, 10:59 am, conman <constantin.christm...@googlemail.com> > > > wrote: > > > > > Yea, I am using appengine patch too and in my logs are a lot deadline > > > > exceeded errors which result from > > > > request on very simple pages without any datastore operations. > > > > > But what's the problem? I have the feeling app engine is lagging at > > > > this time of the day but that may be a oversimplification... > > > > What's your solution to that problem - or are you just igoring it? > > > > > Constantin > > > > > On 7 Feb., 19:37, johnP <j...@thinkwave.com> wrote: > > > > > > I saw similar issues (with a google-issued, non-customized 500 > > > > > deadline exceeded error). I'm using appengine patch, and saw a large > > > > > increase in zipimporter calls. It seemed like a large number of > > > > > requests were reloading the entire Django environment (and maybe doing > > > > > so more slowly than usual...) which resulted in periodic deadline > > > > > exceeded errors on very simple pages. Sound possible? > > > > > > johnP > > > > > > On Feb 7, 9:29 am, conman <constantin.christm...@googlemail.com> > > > > > wrote: > > > > > > > It's happening again!! > > > > > > > Our site is not accessible but instead showing a google 500 server > > > > > > error page!!! > > > > > > > The whole day everything worked normal but in the early evening > > > > > > (Germany/Europe) or forenoon (PST) the serving of the site is broken > > > > > > again - and I definitively didn't change anything today! > > > > > > > Yesterday at the same time of the day app engine had the exact same > > > > > > problem:http://groups.google.com/group/google-appengine/browse_thread/thread/... > > > > > > > What's up with that and where can I report this error so someone at > > > > > > google will look into that? > > > > > > > Regards, > > > > > > 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 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 -~----------~----~----~----~------~----~------~--~---
