Inactivity Monitor timeout does not on disconnected client does not cause
blocked dispatch to client to fail.
-------------------------------------------------------------------------------------------------------------
Key: AMQ-918
URL: https://issues.apache.org/activemq/browse/AMQ-918
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 4.0
Reporter: Hiram Chirino
Assigned To: Hiram Chirino
Fix For: 4.1, 4.0.2
The cause is that inactivity timeout cause an async thread to call
TransportConnection.stop() but it in turn tries to do a "transport.oneway(new
ShutdownInfo());" before a transport.stop();
Since another thread is currently stuck in the oneway() call (due to the client
having disconnected but the OS has not thrown an IOException up to us yet), our
ShutdownInfo message blocks too. So in essence the InactivityMonitor is not
currently shutitng down the failed connections.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
