Indeed, appengine was having a problem and some apps ended up chewing up
quite a bit of instance time in order to fail with the sort of error your
app encountered.
On Friday, March 9, 2012 4:54:51 PM UTC-8, Tony wrote:
>
> Now it says "Your application is at or near its daily budget limit." It
> just stopped serving. And during all day it was flooding me with errors
> like:
>
>
> 1. 2012-03-09 09:55:08.090
>
> Failed startup of context
> com.google.apphosting.utils.jetty.RuntimeAppEngineWebAppContext@537935{/,/base/data/home/apps/crystalupdate/32.356258734295133782}
> com.google.apphosting.api.DeadlineExceededException: This request
> (23186b2f795c1521) started at 2012/03/09 17:54:07.770 UTC and was still
> executing at 2012/03/09 17:55:07.875 UTC.
> at
> com.google.appengine.runtime.Request.process-23186b2f795c1521(Request.java)
> at java.util.zip.ZipFile.read(Native Method)
> at java.util.zip.ZipFile.access$1200(ZipFile.java:57)
> at java.util.zip.ZipFile$ZipFileInputStream.read(ZipFile.java:476)
> at java.util.zip.ZipFile$1.fill(ZipFile.java:259)
> at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:158)
> at sun.misc.Resource.getBytes(Resource.java:124)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:273)
> at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:266)
> at java.lang.Class.getDeclaredConstructors0(Native Method)
> at java.lang.Class.privateGetDeclaredConstructors(Class.java:2406)
> at java.lang.Class.getConstructor0(Class.java:2716)
> at java.lang.Class.newInstance0(Class.java:343)
> at java.lang.Class.newInstance(Class.java:325)
> at org.mortbay.jetty.servlet.Holder.newInstance(Holder.java:153)
> at org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:92)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at
> org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:662)
> at org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
> 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.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 java.lang.Thread.run(Thread.java:679)
>
> 2. C 2012-03-09 09:55:08.194
>
> 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)
>
> 3. I 2012-03-09 09:55:09.391
>
> 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.
>
> 4. W 2012-03-09 09:55:09.391
>
> 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)
>
>
> And now I'm out of money. What's happening? It can't be my fault, why I'm
> paying for this?
>
>
> App ID: crystalupdate
>
--
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/-/wNr2G9vQVOcJ.
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.
