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

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.13.3
• Fix Version/s: 5.13.4, 5.14.0
• Component/s: Broker
• Assignee: Christopher L. Shannon
• Reporter: Christopher L. Shannon
• Created: 05/Jul/16 17:46
• Updated: 06/Jul/16 09:45
• Resolved: 05/Jul/16 18:20

Description

Just like in AMQ-6046, 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 was fixed for Stomp in AMQ-6046 but also needs to be fixed for MQTT.

Issue Links

• relates to: AMQ-6046 Concurrent access to a Transport from WebSocket client can deadlock