On Tuesday, 26 July 2011 04:03:44 UTC+7, Ikai L (Google) wrote: > > John, yeah, it's a deadlock, possibly in userspace code. Can you look into > this? > > The only pattern I could detect was the dead-lock with concurrent file access - I had my web framework in dev mode so each request was loading templates. I do a lot of reflective reads and writes (Method.get Method.set) and annotation reading, which makes me suspect the GAE security manager.
I've run a load test on the dev server and not seen the dead-locks locally. On our end we'll see if we can surface and more usable error message. > > Nice one, a stack trace would really help figure this one out. I'll turn on threadsafe mode again once its possible to get some more details on the problem. I think that running single threaded increases the variance of response times. I often now see a request take e.g. 600ms but my code competes in 50ms. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/YfJhHVZZo70J. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
