Uploaded image for project: 'JBoss Web'
  1. JBoss Web
  2. JBWEB-125

Crash ending an event driven HTTP connection

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Cannot Reproduce
    • Affects Version/s: JBossWeb-2.1.1.GA
    • Fix Version/s: None
    • Component/s: Core
    • Labels:
      None
    • Estimated Difficulty:
      High

      Description

      I experienced a very rare crash when using events (bayeux stock ticker on localhost + F5), when setting back the socket timeout at the end of the processing. The odd part is that it seems to be caught with an exception (very good) but causes a JVM crash anyway.

      Oct 31, 2008 5:31:47 PM org.apache.coyote.http11.Http11AprProcessor event
      SEVERE: Error processing request
      org.apache.tomcat.jni.Error: Socket operation on non-socket
      at org.apache.tomcat.jni.Socket.timeoutSet(Native Method)
      at org.apache.coyote.http11.Http11AprProcessor.action(Http11AprProcessor.java:1262)
      at org.apache.coyote.Response.action(Response.java:184)
      at org.apache.catalina.connector.CoyoteAdapter.event(CoyoteAdapter.java:272)
      at org.apache.coyote.http11.Http11AprProcessor.event(Http11AprProcessor.java:786)
      at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.event(Http11AprProtocol.java:544)
      at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1988)
      at java.lang.Thread.run(Thread.java:636)
      #

      1. An unexpected error has been detected by Java Runtime Environment:
        #
      2. SIGSEGV (0xb) at pc=0x00b43521, pid=5850, tid=101182352
        #
      3. Java VM: OpenJDK Server VM (1.6.0-b09 mixed mode linux-x86)
      4. Problematic frame:
      5. C [libtcnative-1.so.0.1.15+0xf521] Java_org_apache_tomcat_jni_Socket_timeoutSet+0x61
        #
      6. An error report file with more information is saved as:
      7. /home/remm/Work/jbossweb/jbossweb-2.1.x/output/build/hs_err_pid5850.log
        [thread 97975184 also had an error]
        #
      8. If you would like to submit a bug report, please visit:
      9. http://icedtea.classpath.org/bugzilla
      10. The crash happened outside the Java Virtual Machine in native code.
      11. See problematic frame for where to report the bug.
        #

      Assigning to Mladen since the error hints the crash can be avoided (as it seems detected already).

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                mladen.turk Mladen Turk
                Reporter:
                rmaucher Remy Maucherat
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: