I am also seeing this issue. I started to implement a cron task to clean some data periodically. As a first step I added a servlet that only logs that is was executed - nothing else.
In about 1in five runs I get this message. I will usually see this once or twice in a row then the serlet will start running again successfully (taking about 10ms). On Jan 25, 10:29 pm, Don Schwarz <[email protected]> wrote: > We continuously monitor the resource utilization of our servers. In > response to this data, along with several bug reports including the one > mentioned earlier in this thread, we've made a number of configuration > changes to make our serving infrastructure less aggressive about reclaiming > resources and to smooth out hotspots. > > In particular, the application mentioned above was running on one of the > particularly hot servers. We're still measuring the impact of these > changes, but you should have seen better performance over the last few days > and we expect things to continue to improve over time. > > -- Don > > On Sat, Jan 23, 2010 at 5:36 AM, Richard <[email protected]> wrote: > > Could either of you put up an update when you figure out what's > > causing it? Will watch the thread. > > > Regards, > > Richard > > > -- > > 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]<google-appengine-java%[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.
