[jboss-jira] [JBoss JIRA] Closed: (JBAS-4555) Connection.close() taking 2 minutes in JBossMQ

[Adrian Brock (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBAS-4555?page=all ]

Adrian Brock closed JBAS-4555.
------------------------------

    Resolution: Done

I fixed this issue by always closing the socket in the stop().
I am no longer seeing "read timeouts" at random.

> Connection.close() taking 2 minutes in JBossMQ
> ----------------------------------------------
>
>                 Key: JBAS-4555
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4555
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JMS service
>    Affects Versions: JBossAS-4.2.1.GA
>         Environment: Fedora Core 6
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_09-b03)
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira