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

Posted to issues@activemq.apache.org by "clebert suconic (JIRA)" <ji...@apache.org> on 2018/04/30 14:45:00 UTC

[jira] [Moved] (ARTEMIS-1837) Replication catch up dead locks with clients failing

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

clebert suconic moved AMQ-6955 to ARTEMIS-1837:
-----------------------------------------------

    Workflow: jira  (was: classic default workflow)
         Key: ARTEMIS-1837  (was: AMQ-6955)
     Project: ActiveMQ Artemis  (was: ActiveMQ)

> Replication catch up dead locks with clients failing
> ----------------------------------------------------
>
>                 Key: ARTEMIS-1837
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1837
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>            Reporter: clebert suconic
>            Priority: Major
>
> if a client failed during the initial replication catch up, the Netty thread would be used to issue an error and reconnect, but the catchup may be waiting completion. Result is a deadlock freezing both backup and live.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)