Uploaded image for project: 'JBoss Web Server'
  1. JBoss Web Server
  2. JWS-280

Running async example servlet multiple times causes Tomcat crash

    XMLWordPrintable

Details

    • Tomcat no longer fails if the async example servlet is run multiple times.
    • Documented as Resolved Issue
    • Hide

      1) Install JWS with examples.
      2) Try to reach multiple times http://localhost:8080/examples/servlets/nonblocking/numberwriter

      Show
      1) Install JWS with examples. 2) Try to reach multiple times http://localhost:8080/examples/servlets/nonblocking/numberwriter

    Description

      Multiple run of the numberwriter servlet causes crash of tomcat8.

      Catalina.out

      26-Nov-2015 12:56:27.212 SEVERE [http-apr-127.0.0.1-8080-exec-9] org.apache.coyote.http11.AbstractHttp11Processor.endRequest Error finishing response
       org.apache.tomcat.jni.Error: 20005: An invalid socket was returned
              at org.apache.tomcat.jni.Socket.sendbb(Native Method)
              at org.apache.coyote.http11.InternalAprOutputBuffer.writeToSocket(InternalAprOutputBuffer.java:288)
              at org.apache.coyote.http11.InternalAprOutputBuffer.writeToSocket(InternalAprOutputBuffer.java:245)
              at org.apache.coyote.http11.InternalAprOutputBuffer.flushBuffer(InternalAprOutputBuffer.java:214)
              at org.apache.coyote.http11.AbstractOutputBuffer.endRequest(AbstractOutputBuffer.java:378)
              at org.apache.coyote.http11.AbstractHttp11Processor.endRequest(AbstractHttp11Processor.java:1812)
              at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1151)
              at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:668)
              at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:285)
              at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.doRun(AprEndpoint.java:2419)
              at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.run(AprEndpoint.java:2408)
              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
              at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
              at java.lang.Thread.run(Thread.java:745)
      
      26-Nov-2015 12:56:27.213 FINE [http-apr-127.0.0.1-8080-exec-9] org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process Socket: [org.apache.tomcat.util.net.AprEndpoint$AprSocketWrapper@10839f78:139666766468768], Status in: [TIMEOUT], State out: [CLOSED]
      #
      # A fatal error has been detected by the Java Runtime Environment:
      #
      #  SIGSEGV (0xb) at pc=0x00007f0708bd830d, pid=31508, tid=139668107552512
      #
      # JRE version: OpenJDK Runtime Environment (7.0_79-b14) (build 1.7.0_79-mockbuild_2015_05_27_09_36-b00)
      # Java VM: OpenJDK 64-Bit Server VM (24.79-b02 mixed mode linux-amd64 compressed oops)
      # Derivative: IcedTea 2.5.5
      # Distribution: Red Hat Enterprise Linux Server release 6.7 Beta (Santiago), package rhel-2.5.5.4.el6-x86_64 u79-b14
      # Problematic frame:
      # C  [libapr-jws3-1.so.0+0x1930d]  apr_pool_destroy+0xd
      #
      # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
      #
      # An error report file with more information is saved as:
      # /tmp/jvm-31508/hs_error.log
      #
      # If you would like to submit a bug report, please include
      # instructions on how to reproduce the bug and visit:
      #   http://icedtea.classpath.org/bugzilla
      #
      

      Attachments

        Activity

          People

            rhn-support-csutherl Coty Sutherland
            fgoldefu@redhat.com Filip Goldefus (Inactive)
            Jan Štefl Jan Štefl
            Tyler Kelly Tyler Kelly (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: