@Ikai We do have about 1.2 requests/second on our application with the ID "dctptv", so that's probably a good app to debug the problem with. The application is written in Python, using Memcache, URL Fetch, TaskQueue APIs, the Datastore and a zip-imported version of Django 1.2.3.
The whole app has a great test coverage, has been running the same code without problems 24hours ago and is still building successfully on our continuous integration server and running on our development boxes. So I'm pretty sure that's not a problem concerning our code. Furthermore, we deployed a version having Guido van Rossum's AppStats as the first Django middleware, so every request that gets routed through Django directly hits his code (and also does raise Error 500 very often. I don't know if you are able to sign in as a superuser and have a look to the results, but in case you can: http://190-fabian.latest.dctptv.appspot.com/appstats (The default version is "186-fabian", which is running way more stable than "190- fabian", so the version with appstats does not get any requests beside yours). Best regards, Fabian On Sep 23, 10:53 pm, Darien Caldwell <[email protected]> wrote: > all serving for my app is now 100% dead. even the simplest request is > coming up 500 errors. App ID is slconductor. -- 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.
