You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2015/11/17 15:54:11 UTC
[jira] [Created] (AMQ-6046) Concurrent access to a Transport from
WebSocket client can deadlock
Timothy Bish created AMQ-6046:
---------------------------------
Summary: Concurrent access to a Transport from WebSocket client can deadlock
Key: AMQ-6046
URL: https://issues.apache.org/jira/browse/AMQ-6046
Project: ActiveMQ
Issue Type: Bug
Components: MQTT, stomp, Transport
Affects Versions: 5.11.3, 5.12.1, 5.12.0
Reporter: Timothy Bish
Assignee: Timothy Bish
Fix For: 5.13.0
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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)