I am also noticing that for no reason, additional instances are getting created. Every 2-3 minutes, I see '/_ah/warmup' messages in the info logs
-Aswath On Wed, Apr 20, 2011 at 5:19 PM, Aswath Satrasala < aswath.satras...@gmail.com> wrote: > Hello, > My app-id has 'Always on' enabled > Our app-id activity has increased. I am noticing 2-3 related issues. > * I am seeing many many "/_ah/warmup " in the logs. (maybe our app-id > activity is increased) > * A lot of these are throwing 'DeadlineExceededException'. > * Why should that exception be thrown for some and not thrown for few > /_ah/warmup. > > My logs are filled with above messages and errors.I feel something unusual > here. > > -Aswath > > 2011-04-20 04:39:18.446 /_ah/warmup 500 48134ms 6953cpu_ms 0kb > > 1. > 1. See > details<https://appengine.google.com/logs/log_detail?app_id=vs-accounting&version_id=9.349708795707059392&request_id=0004A15813379630.DB796813&layout=plain> > > 0.1.0.3 - - [20/Apr/2011:04:39:18 -0700] "GET /_ah/warmup HTTP/1.1" 500 > 0 - - "9.349708795707059392.vs-accounting.appspot.com" ms=48135 cpu_ms=6953 > api_cpu_ms=0 cpm_usd=0.193164 exit_code=104 throttle_code=1 > > 2. W 2011-04-20 04:38:59.058 > > com.veersoft.listener.VsServletContextListener contextInitialized: > 2011-04-20 17:08:59 IST > > 3. C 2011-04-20 04:39:18.426 > > Uncaught exception from servlet > com.google.apphosting.runtime.HardDeadlineExceededError: This request > (b3f5ddbb056640c9) started at 2011/04/20 11:38:31.643 UTC and was still > executing at 2011/04/20 11:39:18.417 UTC. > > at > com.google.appengine.runtime.Request.process-b3f5ddbb056640c9(Request.java) > at java.lang.ClassLoader.loadClass(ClassLoader.java:266) > at > com.veersoft.listener.VsServletContextListener.registerEntities(VsServletContextListener.java:76) > > at > com.veersoft.listener.VsServletContextListener.contextInitialized(VsServletContextListener.java:67) > at > org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:548) > at > org.mortbay.jetty.servlet.Context.startContext(Context.java:136) > > at > org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1250) > at > org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517) > at > org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467) > > at > org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) > at > com.google.net.rpc.impl.RpcUtil.runRpcInApplication(RpcUtil.java:437) > at > com.google.net.rpc.impl.Server$RpcTask.runInContext(Server.java:573) > > at > com.google.tracing.TraceContext$TraceContextRunnable$1.run(TraceContext.java:448) > at > com.google.tracing.TraceContext.runInContext(TraceContext.java:688) > at > com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContextNoUnref(TraceContext.java:326) > > at > com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContext(TraceContext.java:318) > at > com.google.tracing.TraceContext$TraceContextRunnable.run(TraceContext.java:446) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:636) > > 4. W 2011-04-20 04:39:18.438 > > A serious problem was encountered with the process that handled this > request, causing it to exit. This is likely to cause a new process to be used > for the next request to your application. If you see this message frequently, > you may be throwing exceptions during the initialization of your application. > (Error code 104) > > > > -- 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 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.
