No, there's nothing in the deployed logs indicating an error (or in the local console info). In fact, in the deployed logs I do see that 'appstats available' message for those requests, e.g. Appstats available: /appstats/details?time=1272409799843 but get a 'not found' error when I follow the link.
But, it sounds feasible that something along those lines could be happening somewhere, and perhaps the exception is being swallowed. (I wonder if it could be memcache-related?...) On Apr 27, 1:05 pm, Jens Scheffler <[email protected]> wrote: > Hi, > > If you look at the logs of your deployed application, do you see any > errors, such as an OutOfMemoryError? My current suspicion is that app > stats collects so much data (and keeps it in memory) for this request > that it runs out of memory before it can persist it. If that is the > case, we might be seeing something like that in the error logs. > > Best regards, > > Jens > > On Apr 27, 10:01 am, Dick Johnson <[email protected]> wrote: > > > As an addendum to my previous note-- when an app is deployed to App > > Engine, I don't get the appstats 'hang' behaviour of my previous post, > > in that the servlet response does finish rendering. But, just as with > > the local development version, the servlets that caused issues with > > Appstats are not listed at all in the Appstats statistics page for the > > deployed version. For some reason, these servlets are not getting > > properly processed by Appstats. > > > This seems especially problematic because the servlets in question, > > that are not being reported by appstats, are in actuality taking up > > the largest percentage of resources. > -- 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.
