So, apparently, we all imagined the problem. The status page no longer admits to anything.
A. On Tue, Mar 6, 2012 at 4:44 PM, Francois Masurel <f.masu...@gmail.com> wrote: > Yep, getting quite a few errors on loading requests lately like this one for > example : > > 2012-03-06 20:26:42.834 > > Uncaught exception from servlet > org.apache.xerces.parsers.ObjectFactory$ConfigurationError: Provider > org.apache.xerces.parsers.XIncludeAwareParserConfiguration could not be > instantiated: com.google.apphosting.api.DeadlineExceededException: This > request (c2d42bb1d5647665) started at 2012/03/06 19:25:43.000 UTC and was > still executing at 2012/03/06 19:26:42.782 UTC. > at org.apache.xerces.parsers.ObjectFactory.newInstance(Unknown Source) > at org.apache.xerces.parsers.ObjectFactory.createObject(Unknown Source) > at org.apache.xerces.parsers.ObjectFactory.createObject(Unknown Source) > at org.apache.xerces.parsers.SAXParser.<init>(Unknown Source) > at org.apache.xerces.parsers.SAXParser.<init>(Unknown Source) > at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.<init>(Unknown > Source) > at org.apache.xerces.jaxp.SAXParserImpl.<init>(Unknown Source) > at org.apache.xerces.jaxp.SAXParserImpl.<init>(Unknown Source) > at org.apache.xerces.jaxp.SAXParserFactoryImpl.newSAXParserImpl(Unknown > Source) > at org.apache.xerces.jaxp.SAXParserFactoryImpl.setFeature(Unknown > Source) > at org.mortbay.xml.XmlParser.makeFactorySecure(XmlParser.java:162) > at org.mortbay.xml.XmlParser.setValidating(XmlParser.java:102) > at org.mortbay.xml.XmlParser.<init>(XmlParser.java:91) > at > org.mortbay.jetty.webapp.TagLibConfiguration.configureWebApp(TagLibConfiguration.java:210) > at > org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1247) > 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) > > I2012-03-06 20:26:42.879 > > 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. > > W2012-03-06 20:26:42.879 > > 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) > > > On Tuesday, March 6, 2012 10:17:37 PM UTC+1, Adam Sherman wrote: >> >> Am I the only one seeing short duration outages? They are being reflected >> at: >> >> http://code.google.com/status/appengine >> >> But I don't see anyone else complaining anywhere, so it makes me worried. >> >> A. >> > -- > 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/-/BCIjV778ufoJ. > > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. -- Adam Sherman, CTO Versature Corp. / +1.877.498.3772 x113 Follow us on Twitter - http://twitter.com/Versature Check out the Versature Blog - http://inside.versature.com -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
