It is possible that you are running into deadlocks when you set threadsafe=true. As of a few days ago you should begin seeing stack traces in your logs if we detect a deadlock at the end of a request.
On Fri, Sep 9, 2011 at 10:26 AM, Nick Rudnik <[email protected]> wrote: > I see the same behavior on warmup requests but only when threadsafe=true. If > I leave threadsafe set to false, my warmup requests never have deadline > exceeded errors. This is very troubling because we really need > threadsafe=true in light of the new pricing. > I can't find a good explanation for this. > > -- > 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/-/GkjrMGPu-ZIJ. > 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-java?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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-java?hl=en.
