[AMQ-5794] Cleanup connections that open but don't initiate a protocol handshake.

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.10.0, 5.10.1, 5.10.2, 5.11.0, 5.11.1
• Fix Version/s: 5.12.0
• Component/s: JMS client, STOMP, Transport
• Assignee: Timothy A. Bish
• Reporter: Timothy A. Bish
• Created: 22/May/15 20:36
• Updated: 25/Apr/16 08:56
• Resolved: 26/May/15 16:30

Description

The current inactivity monitor implementation only kicks in when the connection is opened an the protocol handshake completes such as when an OpenWire client sends its WireFormatInfo or when a STOMP client sends the CONNECT frame.

We currently deal with this case for AMQP and MQTT by using a connection attempt timeout to close down connections that have opened but not started a handshake. We should extend this to STOMP and OpenWire as well.

This issue has been seen in the STOMP over websockets where a STOMP WebSocket connection is opened but for some reason never initiates.

Issue Links

• breaks: AMQ-6262 HTTP transport broken in 5.12
• is related to: AMQ-4955 TCP Connections and related thread leak.