https://bz.apache.org/bugzilla/show_bug.cgi?id=66600

            Bug ID: 66600
           Summary: NPE in certain scenarios
           Product: Tomcat 9
           Version: 9.0.75
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Catalina
          Assignee: dev@tomcat.apache.org
          Reporter: boris_pet...@live.com
  Target Milestone: -----

I'm not exactly sure when. I think it happens when some requests that take a
very long time in the beginning (before some caches are populated). Here is a
stacktrace:

ERROR o.g.j.server.ServerRuntime$Responder - Error while closing the output
stream in order to commit response.
java.lang.NullPointerException: Cannot invoke
"org.apache.tomcat.util.net.SocketWrapperBase.flush(boolean)" because
"this.this$0.socketWrapper" is null
        at
org.apache.coyote.http11.Http11OutputBuffer$SocketOutputBuffer.flush(Http11OutputBuffer.java:566)
        at
org.apache.coyote.http11.filters.ChunkedOutputFilter.flush(ChunkedOutputFilter.java:157)
        at
org.apache.coyote.http11.Http11OutputBuffer.flush(Http11OutputBuffer.java:220)
        at
org.apache.coyote.http11.Http11Processor.flush(Http11Processor.java:1246)
        at
org.apache.coyote.AbstractProcessor.action(AbstractProcessor.java:398)
        at org.apache.coyote.Response.action(Response.java:207)
        at
org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:305)
        at
org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:271)
        at
org.apache.catalina.connector.CoyoteOutputStream.flush(CoyoteOutputStream.java:118)
        at
org.glassfish.jersey.servlet.internal.ResponseWriter$NonCloseableOutputStreamWrapper.flush(ResponseWriter.java:307)
        at
org.glassfish.jersey.message.internal.CommittingOutputStream.flush(CommittingOutputStream.java:263)
        at
org.glassfish.jersey.message.internal.OutboundMessageContext.close(OutboundMessageContext.java:864)
        at
org.glassfish.jersey.server.ContainerResponse.close(ContainerResponse.java:389)
        at
org.glassfish.jersey.server.ServerRuntime$Responder.writeResponse(ServerRuntime.java:721)
        at
org.glassfish.jersey.server.ServerRuntime$Responder.processResponse(ServerRuntime.java:380)
        at
org.glassfish.jersey.server.ServerRuntime$Responder.process(ServerRuntime.java:370)
        at
org.glassfish.jersey.server.ServerRuntime$AsyncResponder$3.run(ServerRuntime.java:871)
        at org.glassfish.jersey.internal.Errors$1.call(Errors.java:248)
        at org.glassfish.jersey.internal.Errors$1.call(Errors.java:244)
        at org.glassfish.jersey.internal.Errors.process(Errors.java:292)
        at org.glassfish.jersey.internal.Errors.process(Errors.java:274)
        at org.glassfish.jersey.internal.Errors.process(Errors.java:244)
        at
org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:265)
        at
org.glassfish.jersey.server.ServerRuntime$AsyncResponder.resume(ServerRuntime.java:903)
        at
org.glassfish.jersey.server.ServerRuntime$AsyncResponder.resume(ServerRuntime.java:859)
        ...

Any ideas? Is that a bug in Tomcat or I've done something wrong?

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to