[AMQ-6046] Concurrent access to a Transport from WebSocket client can deadlock

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.12.0, 5.12.1, 5.11.3
• Fix Version/s: 5.13.0
• Component/s: MQTT, STOMP, Transport
• Assignee: Timothy A. Bish
• Reporter: Timothy A. Bish
• Created: 17/Nov/15 14:53
• Updated: 05/Jul/16 18:20
• Resolved: 17/Nov/15 16:28

Description

WebSocket connections can encounter a deadlock when the Jetty side allows for concurrent access to the Transport instance that forwards commands onto the broker core. This seems to happen mostly in cases where a message or other action is incoming at the same time as Jetty is closing the connection due to idle timeout or some other cause.

Issue Links

• is related to: AMQ-6346 Concurrent access to a MQTT Transport from WebSocket client can deadlock