[ https://issues.apache.org/jira/browse/ARTEMIS-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16542018#comment-16542018 ]
ASF subversion and git services commented on ARTEMIS-1966: ---------------------------------------------------------- Commit 2a30b291be94b0283172b15fa573b86769a32070 in activemq-artemis's branch refs/heads/master from Clebert Suconic [ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=2a30b29 ] ARTEMIS-1966 Improving SharedNothingReplicationFlowControlTest Tests should always extend ActiveMQTestBase whenever is possible. This is because there are a few rules to avoid thread leakages. The test was also leaking an executor and I believe it was not always stopping the servers, which I fixed here. > Replication channel closed but not connection if flow controlled during > replication > ----------------------------------------------------------------------------------- > > Key: ARTEMIS-1966 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1966 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker > Affects Versions: 2.6.2 > Reporter: yangwei > Priority: Major > > We use SharedNothing Activation. If flow control occurs during replication, > replication channel would be closed and enabled flagĀ is set to false. After > it, the message would not be sent to backup node. If live server crashes at > this time, the backup node will fail over, resulting in data loss. > So we close connection if flow controlled, then backup node would be signaled > failure replicating and restart server. -- This message was sent by Atlassian JIRA (v7.6.3#76005)