Hey Googlers,
Do you know why we get these DeadlineExceededException when Jetty's trying
to load session data from the datastore ?
It looks like a bug as there is only Google App Engine code being executed
here (see stacktrace below).
And (still haven't got an answer about that) why does it have to kill and
restart the instance when such exceptions occurs ? Doesn't seem to be
optimal in threadsafe mode.
Thanx for your help.
Francois
1. 2011-05-17 02:00:14.483
Nested in javax.servlet.ServletException:
com.google.apphosting.api.DeadlineExceededException: This request
(fb27bd896bd3c1f8) started at 2011/05/17 08:59:44.654 UTC and was still
executing at 2011/05/17 09:00:14.465 UTC.:
com.google.apphosting.api.DeadlineExceededException: This request
(fb27bd896bd3c1f8) started at 2011/05/17 08:59:44.654 UTC and was still
executing at 2011/05/17 09:00:14.465 UTC.
at sun.misc.Unsafe.park(Native Method)
at
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1326)
at
com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:232)
at
com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:69)
at
com.google.appengine.tools.development.TimedFuture.get(TimedFuture.java:41)
at
com.google.common.util.concurrent.ForwardingFuture.get(ForwardingFuture.java:64)
at
com.google.appengine.api.utils.FutureWrapper.get(FutureWrapper.java:67)
at
com.google.appengine.api.datastore.FutureHelper$CumulativeAggregateFuture.get(FutureHelper.java:136)
at
com.google.appengine.api.datastore.FutureHelper.getInternal(FutureHelper.java:71)
at
com.google.appengine.api.datastore.FutureHelper.quietGet(FutureHelper.java:32)
at
com.google.appengine.api.datastore.DatastoreServiceImpl$1.runInternal(DatastoreServiceImpl.java:78)
at
com.google.appengine.api.datastore.DatastoreServiceImpl$1.runInternal(DatastoreServiceImpl.java:75)
at
com.google.appengine.api.datastore.TransactionRunner.runInTransaction(TransactionRunner.java:31)
at
com.google.appengine.api.datastore.DatastoreServiceImpl.get(DatastoreServiceImpl.java:75)
at
com.google.appengine.api.datastore.DatastoreServiceImpl.get(DatastoreServiceImpl.java:62)
at
com.google.apphosting.runtime.jetty.SessionManager.loadSession(SessionManager.java:318)
at
com.google.apphosting.runtime.jetty.SessionManager.getSession(SessionManager.java:288)
at
org.mortbay.jetty.servlet.AbstractSessionManager.getHttpSession(AbstractSessionManager.java:237)
at
org.mortbay.jetty.servlet.SessionHandler.setRequestedId(SessionHandler.java:246)
at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:136)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
at
com.google.apphosting.runtime.jetty.AppVersionHandlerMap.handle(AppVersionHandlerMap.java:238)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
at
org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:923)
at
com.google.apphosting.runtime.jetty.RpcRequestParser.parseAvailable(RpcRequestParser.java:76)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at
com.google.apphosting.runtime.jetty.JettyServletEngineAdapter.serviceRequest(JettyServletEngineAdapter.java:135)
at
com.google.apphosting.runtime.JavaRuntime.handleRequest(JavaRuntime.java:260)
at
com.google.apphosting.base.RuntimePb$EvaluationRuntime$2.handleRequest(RuntimePb.java:9669)
at com.google.net.rpc.impl.RpcUtil.runRpcInApplication(RpcUtil.java:439)
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)
2. W2011-05-17 02:00:14.488
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 [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.
