uploads to our server failing with Operand stack overflow. Exceeded max stack size.

[Brian Miller]

Looking for assistance from Google Cloud infrastructure team for the following issue.

We started seeing failures with two of our file upload servlets hosted in a Google App Engine project,

at about 5:50 PM Pacific Time Wednesday night, September 5, 2018.

We did NOT do a new deployment recently, so code is the same as what was working shortly before that.

This is the server error we are seeing now:

java.lang.VerifyError: Operand stack overflow

Reason:

    Exceeded max stack size.

at java.lang.Class.getDeclaredConstructors0(Native Method)

at java.lang.Class.privateGetDeclaredConstructors(Class.java:2591)

at java.lang.Class.getConstructor0(Class.java:2943)

at java.lang.Class.newInstance(Class.java:350)

at org.mortbay.jetty.servlet.Holder.newInstance(Holder.java:153)

at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:428)

at org.mortbay.jetty.servlet.ServletHolder.getServlet(ServletHolder.java:339)

at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)

at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166)

at com.google.apphosting.utils.servlet.ParseBlobUploadFilter.doFilter(ParseBlobUploadFilter.java:125)

at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)

at com.google.apphosting.runtime.jetty.SaveSessionFilter.doFilter(SaveSessionFilter.java:37)

at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)

at com.google.apphosting.utils.servlet.JdbcMySqlConnectionCleanupFilter.doFilter(JdbcMySqlConnectionCleanupFilter.java:60)

at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)

at com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(TransactionCleanupFilter.java:48)

at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)

at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)

at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)

at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)

at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)

at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)

at com.google.apphosting.runtime.jetty.AppVersionHandlerMap.handle(AppVersionHandlerMap.java:257)

at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)

at org.mortbay.jetty.Server.handle(Server.java:326)

at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)

at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:923)

at com.google.apphosting.runtime.jetty.RpcRequestParser.parseAvailable(RpcRequestParser.java:76)

at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)

at com.google.apphosting.runtime.jetty.JettyServletEngineAdapter.serviceRequest(JettyServletEngineAdapter.java:146)

at com.google.apphosting.runtime.JavaRuntime$RequestRunnable.dispatchServletRequest(JavaRuntime.java:692)

at com.google.apphosting.runtime.JavaRuntime$RequestRunnable.dispatchRequest(JavaRuntime.java:654)

at com.google.apphosting.runtime.JavaRuntime$RequestRunnable.run(JavaRuntime.java:624)

at com.google.tracing.TraceContext$TraceContextRunnable.runInContext(TraceContext.java:455)

at com.google.tracing.TraceContext$TraceContextRunnable$1.run(TraceContext.java:462)

at com.google.tracing.CurrentContext.runInContext(CurrentContext.java:320)

at com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContextNoUnref(TraceContext.java:321)

at com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContext(TraceContext.java:313)

at com.google.tracing.TraceContext$TraceContextRunnable.run(TraceContext.java:459)

at com.google.apphosting.runtime.ThreadGroupPool$PoolEntry.run(ThreadGroupPool.java:274)

at java.lang.Thread.run(Thread.java:745)

[Katayoon (Cloud Platform Support)]

I don’t see any incident been reported for App Engine on September 5,2018 in Google Cloud Status Dashboard, however you may open a report in the Issue Tracker and provide us with the first two digits of your project number so that we would be able to dig into the issue.

- Note that Google Groups are reserved for general Google Cloud Platform-end product discussions and not for reporting issues.