[
https://issues.apache.org/jira/browse/AMQ-6346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15362932#comment-15362932
]
ASF subversion and git services commented on AMQ-6346:
------------------------------------------------------
Commit 1dfd0eeb60921243bec8245edb16c07ca98c1857 in activemq's branch
refs/heads/activemq-5.13.x from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=1dfd0ee ]
https://issues.apache.org/jira/browse/AMQ-6346
Prevent concurrent access to the MQTT protocol handlers which can lead
to a tansport level deadlock
(cherry picked from commit 96494f74c7142c3396f17696f345c2355c16a61c)
> Concurrent access to a MQTT Transport from WebSocket client can deadlock
> ------------------------------------------------------------------------
>
> Key: AMQ-6346
> URL: https://issues.apache.org/jira/browse/AMQ-6346
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.13.3
> Reporter: Christopher L. Shannon
> Assignee: Christopher L. Shannon
> Fix For: 5.14.0, 5.13.4
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
