突然，在没有任何警告的情况下，我的AppEngine项目将不再加载到浏览器中。 http://my.loopto.do。旧版本的应用程序也会发生这种情况。以下是500错误。
我知道DeadlineExceededException是什么。我不明白的是为什么会发生这种情况，即使在以前工作正常但没有问题的版本上也是如此。日志一直转到ALL，似乎没有说明问题是什么。
另一个有趣的观点是，相同的代码库在上传到其他appspot域时会加载而不会出现问题。
- 因此，代码在一个appspot域上运行，但不在另一个域上运行，将代码隔离为常量。 - 此外，之前在破坏的appspot域上工作的旧版本也遇到HardDeadlineExceededError。 - 应用程序还可以使用最新的SDK 1.6.2.1在localhost上正常加载。
我认为这是一个Appengine问题，因为日志没有显示我的代码正在破坏的位置。
我需要做些什么才能解决此问题？
这是StackTrace：
2012-02-23 12:50:06.744 /loop/?t=1330030019399 500 187376ms 1kb Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1
50.43.101.83 - user.name [23/Feb/2012:12:50:06 -0800] "GET /loop/?t=1330030019399 HTTP/1.1" 500 1309 "http://0-9-2012-2-23.loopaback.appspot.com/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1" "0-9-2012-2-23.loopaback.appspot.com" ms=187376 cpu_ms=560 api_cpu_ms=0 cpm_usd=0.015809 loading_request=1 pending_ms=13 exit_code=104 instance=00c61b117c1a26c7b1ad046194db91806cb9d7
W 2012-02-23 12:50:06.616
Failed startup of context com.google.apphosting.utils.jetty.RuntimeAppEngineWebAppContext@fe2558{/,/base/data/home/apps/s~loopaback/0-9-2012-2-23.357026711120155741}
com.google.apphosting.api.DeadlineExceededException: This request (c567eadbd5f794fd) started at 2012/02/23 20:47:09.524 UTC and was still executing at 2012/02/23 20:49:56.454 UTC.
at java.util.zip.ZipFile.getNextEntry(Native Method)
at java.util.zip.ZipFile.access$400(ZipFile.java:57)
at java.util.zip.ZipFile$2.nextElement(ZipFile.java:342)
at java.util.zip.ZipFile$2.nextElement(ZipFile.java:328)
at java.util.jar.JarFile$1.nextElement(JarFile.java:240)
at java.util.jar.JarFile$1.nextElement(JarFile.java:235)
at sun.misc.URLClassPath$JarLoader.addJarEntriesToEntryMap(URLClassPath.java:813)
at sun.misc.URLClassPath$JarLoader.access$1600(URLClassPath.java:723)
at sun.misc.URLClassPath$JarLoader$1.run(URLClassPath.java:900)
at java.security.AccessController.doPrivileged(Native Method)
at sun.misc.URLClassPath$JarLoader.ensureOpenSynchronized(URLClassPath.java:846)
at sun.misc.URLClassPath$JarLoader.ensureOpen(URLClassPath.java:838)
at sun.misc.URLClassPath$JarLoader.<init>(URLClassPath.java:785)
at sun.misc.URLClassPath$JarLoader.<init>(URLClassPath.java:743)
at sun.misc.URLClassPath$3.run(URLClassPath.java:412)
at java.security.AccessController.doPrivileged(Native Method)
at sun.misc.URLClassPath.getLoader(URLClassPath.java:395)
at sun.misc.URLClassPath.getLoader(URLClassPath.java:371)
at sun.misc.URLClassPath.findResource(URLClassPath.java:201)
at java.net.URLClassLoader$2.run(URLClassLoader.java:379)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findResource(URLClassLoader.java:376)
at com.google.apphosting.runtime.security.UserClassLoader.findResource(UserClassLoader.java:723)
at java.lang.ClassLoader.getResource(ClassLoader.java:977)
at org.mortbay.resource.Resource.newSystemResource(Resource.java:203)
at org.mortbay.jetty.webapp.WebXmlConfiguration.configureDefaults(WebXmlConfiguration.java:159)
at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1230)
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.apphosting.runtime.jetty.AppVersionHandlerMap.createHandler(AppVersionHandlerMap.java:202)
at com.google.apphosting.runtime.jetty.AppVersionHandlerMap.getHandler(AppVersionHandlerMap.java:171)
at com.google.apphosting.runtime.jetty.JettyServletEngineAdapter.serviceRequest(JettyServletEngineAdapter.java:123)
at com.google.apphosting.runtime.JavaRuntime$RequestRunnable.run(JavaRuntime.java:422)
at com.google.tracing.TraceContext$TraceContextRunnable.runInContext(TraceContext.java:449)
at com.google.tracing.TraceContext$TraceContextRunnable$1.run(TraceContext.java:455)
at com.google.tracing.TraceContext.runInContext(TraceContext.java:695)
at com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContextNoUnref(TraceContext.java:333)
at com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContext(TraceContext.java:325)
at com.google.tracing.TraceContext$TraceContextRunnable.run(TraceContext.java:453)
at com.google.apphosting.runtime.ThreadGroupPool$PoolEntry.run(ThreadGroupPool.java:251)
at java.lang.Thread.run(Thread.java:679)
C 2012-02-23 12:50:06.630
Uncaught exception from servlet
javax.servlet.UnavailableException: Initialization failed.
at com.google.apphosting.runtime.jetty.AppVersionHandlerMap.createHandler(AppVersionHandlerMap.java:211)
at com.google.apphosting.runtime.jetty.AppVersionHandlerMap.getHandler(AppVersionHandlerMap.java:171)
at com.google.apphosting.runtime.jetty.JettyServletEngineAdapter.serviceRequest(JettyServletEngineAdapter.java:123)
at com.google.apphosting.runtime.JavaRuntime$RequestRunnable.run(JavaRuntime.java:422)
at com.google.tracing.TraceContext$TraceContextRunnable.runInContext(TraceContext.java:449)
at com.google.tracing.TraceContext$TraceContextRunnable$1.run(TraceContext.java:455)
at com.google.tracing.TraceContext.runInContext(TraceContext.java:695)
at com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContextNoUnref(TraceContext.java:333)
at com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContext(TraceContext.java:325)
at com.google.tracing.TraceContext$TraceContextRunnable.run(TraceContext.java:453)
at com.google.apphosting.runtime.ThreadGroupPool$PoolEntry.run(ThreadGroupPool.java:251)
at java.lang.Thread.run(Thread.java:679)
I 2012-02-23 12:50:06.702
This request caused a new process to be started for your application, and thus caused your application code to be loaded for the first time. This request may thus take longer and use more CPU than a typical request for your application.
W 2012-02-23 12:50:06.702
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)