You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Martyn Taylor (JIRA)" <ji...@apache.org> on 2016/06/07 16:18:21 UTC
[jira] [Assigned] (ARTEMIS-456) Potential dead lock in
ReplicationManager
[ https://issues.apache.org/jira/browse/ARTEMIS-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martyn Taylor reassigned ARTEMIS-456:
-------------------------------------
Assignee: Martyn Taylor
> Potential dead lock in ReplicationManager
> -----------------------------------------
>
> Key: ARTEMIS-456
> URL: https://issues.apache.org/jira/browse/ARTEMIS-456
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Martyn Taylor
> Assignee: Martyn Taylor
> Priority: Critical
> Fix For: 1.3.0
>
>
> There is a potential deadlock in the replication manager. This can be caused when 2 threads try to get locks on the NettyConnection readyListener queue and the replicationLock in opposite order.
> This happens when sendReplicatePacket() and Netty readyForWrite() callback is made.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)