Hi GAE guys, same issue for us ... please react ... our cutomers are complaining :-(
appid: logos-contacts Regards Vincent 1. 2012-03-12 11:31:23.508 /_ah/login_required?continue=https://logos-contacts.appspot.com/500 72138ms 0kb Mozilla/5.0 (Windows NT 5.1) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.60 Safari/534.24 124.148.222.42 - - [12/Mar/2012:04:31:23 -0700] "GET /_ah/login_required?continue=https://logos-contacts.appspot.com/ HTTP/1.1" 500 0 "from customer intranet" "Mozilla/5.0 (Windows NT 5.1) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.60 Safari/534.24" "logos-contacts.appspot.com" ms=72138 cpu_ms=887 api_cpu_ms=0 cpm_usd=0.024681 loading_request=1 exit_code=104 instance=00c61b117c5f903ba6921dbd52f633545a72631c <https://appengine.google.com/instances?app_id=logos-contacts&version_id=v12.357205322028193482&key=00c61b117c5f903ba6921dbd52f633545a72631c#00c61b117c5f903ba6921dbd52f633545a72631c> 2. W2012-03-12 11:31:22.323 Failed startup of context com.google.apphosting.utils.jetty.RuntimeAppEngineWebAppContext@3aa791{/,/base/data/home/apps/logos-contacts/v12.357205322028193482} com.google.apphosting.api.DeadlineExceededException: This request (0746107fc018dfa5) started at 2012/03/12 11:30:21.209 UTC and was still executing at 2012/03/12 11:31:21.935 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: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) 3. C2012-03-12 11:31:22.345 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) 4. I2012-03-12 11:31:22.669 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. 5. W2012-03-12 11:31:22.669 A 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) Le lundi 12 mars 2012 13:17:05 UTC+1, Thomas a écrit : > We experience Google AppEngine having very poor performance / high > latency since about 2 weeks. Even the most basic requests take 1-2s, > going up to over 60s which is totally unacceptable from a user's point > of view. At the same time, about 1-2% of all requests are failing > (without any app-internal reason). Our paying (!) users are beginning > to complain and ask for a fix. Yet, we're totally dependent on > Google's mercy to solve this problem. > > SO PLEASE GOOGLE: do something about it! > THANK YOU!! > > appid: typescout > > Regards, > Thomas -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/YWVSHrVZA40J. 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?hl=en.
