[
https://issues.apache.org/jira/browse/AMQ-6046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15008945#comment-15008945
]
ASF subversion and git services commented on AMQ-6046:
------------------------------------------------------
Commit caa6b8e2539132999045c3fbbd627a2dc6d0885c in activemq's branch
refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=caa6b8e ]
https://issues.apache.org/jira/browse/AMQ-6046
Prevent concurrent access to protocol handlers which can lead to
transport level deadlocks.
> 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.12.0, 5.12.1, 5.11.3
> 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)
