Uploaded image for project: 'Application Server 3  4  5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-4555

Connection.close() taking 2 minutes in JBossMQ

    XMLWordPrintable

    Details

      Description

      For some reason I haven't investigated Thread.interupt() is not interupting I/O reads.

      The JBossMQ UIL2 does this to stop the ReadTask which in turn closes the socket.

      This can be see in the following test run:
      http://cruisecontrol.jboss.com/cc/artifacts/jboss-4.2-testsuite-sun-1.5/20070716040519/results/index.html
      where some tests are timing out or taking 2 minutes.

      Without the interuppted I/O the ReadTask will wait until the "Read Timeout" (default 2 minutes)
      to end because at this point the client has stopped pinging.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  adrian.brock Adrian Brock
                  Reporter:
                  adrian.brock Adrian Brock
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: