Hello! We have such problem: suddenly default instances of our app can't be started because of long first request (actually start of the instance). But: the same code runs OK on not HRD app, and on backend instance (128MB, 600MHz) of the HRD app. Backend instance is up for 10 seconds, so more than 60 sec. up of default instance is really wierd. Logs are attached. I assume it is some AppEngine issues, could you please have a look at it? HRD App Id: prefgame Master-slave: pref-online
-- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/vYdUKyQAvjwJ. 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.
91.221.166.69 - - [04/Nov/2011:07:31:06 -0700] "POST /protopref/gwt/stateService.rpc HTTP/1.1" 500 0 "http://prefgame.appspot.com/"; "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.106 Safari/535.2" "prefgame.appspot.com" ms=95628 cpu_ms=583 api_cpu_ms=0 cpm_usd=0.016274 loading_request=1 exit_code=104 instance=00c61b117c08cfeb57a527d3da7d09368f8784 W 2011-11-04 16:31:05.866 Failed startup of context com.google.apphosting.utils.jetty.RuntimeAppEngineWebAppContext@1970ae0{/,/base/data/home/apps/s~prefgame/1.354446190505933836} com.google.apphosting.api.DeadlineExceededException: This request (0000000000000000) started at 2011/11/04 14:30:04.737 UTC and was still executing at 2011/11/04 14:31:04.499 UTC. at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.<init>(ZipFile.java:143) at java.util.jar.JarFile.<init>(JarFile.java:150) at java.util.jar.JarFile.<init>(JarFile.java:87) at sun.misc.URLClassPath$JarLoader.getJarFile(URLClassPath.java:919) at sun.misc.URLClassPath$JarLoader.access$900(URLClassPath.java:723) at sun.misc.URLClassPath$JarLoader$1.run(URLClassPath.java:854) 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:392) 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:162) at java.lang.Thread.run(Thread.java:679) C 2011-11-04 16:31:05.871 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:392) 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:162) at java.lang.Thread.run(Thread.java:679) I 2011-11-04 16:31:05.881 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 2011-11-04 16:31:05.881 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)
