[#AMQ-918] Inactivity Monitor timeout does not on disconnected client does not cause blocked dispatch to client to fail. - Apache ActiveMQ, Apache ServiceMix, Apache Camel

ActiveMQ

Inactivity Monitor timeout does not on disconnected client does not cause blocked dispatch to client to fail.

Created: 13/Sep/06 11:41 AM Updated: 14/Sep/06 04:33 PM

Return to search

Component/s:

None

Affects Version/s:

4.0

Fix Version/s:

4.0, 4.1.0

Time Tracking:

Not Specified

Description

« Hide

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.

All

Comments

Work Log

Change History

Subversion Commits

FishEye

Crucible

Sort Order:

[ Permlink | « Hide ]

Jonas Lim added a comment - 14/Sep/06 12:44 AM

fixed applied in 4.x branches and trunk (r443267)

Jonas Lim made changes - 14/Sep/06 12:44 AM

Field	Original Value	New Value
Fix Version/s		4.0.1 [ 11780 ]
Status	Open [ 1 ]	Resolved [ 5 ]
Resolution		Fixed [ 1 ]
Fix Version/s		4.0 [ 11660 ]

[ Permlink | « Hide ]

Jonas Lim added a comment - 14/Sep/06 04:33 PM

Edited fix versions to 4.1 and 4.0 only.

4.1 trunk (r443267)
4.0 branch (r443273)

Jonas Lim made changes - 14/Sep/06 04:33 PM

Fix Version/s	4.0.2 [ 11783 ]
Fix Version/s	4.0.1 [ 11780 ]