You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Christopher L. Shannon (JIRA)" <ji...@apache.org> on 2016/07/05 18:20:11 UTC

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

     [ https://issues.apache.org/jira/browse/AMQ-6346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christopher L. Shannon resolved AMQ-6346.
-----------------------------------------
       Resolution: Fixed
    Fix Version/s: 5.13.4
                   5.14.0

> 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)