[
https://issues.apache.org/jira/browse/ARTEMIS-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16546573#comment-16546573
]
ASF subversion and git services commented on ARTEMIS-1966:
----------------------------------------------------------
Commit e4ccbb929b722a31af2d14f17e4c96d6bbe2b10e in activemq-artemis's branch
refs/heads/2.6.x from yang wei
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=e4ccbb9 ]
ARTEMIS-1966 Replication channel closed but not connection if flow controlled
during replication
(cherry picked from commit 9f8288c0156072b3ae02efd04e1adbcd0abca2c2)
> 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
> Fix For: 2.7.0, 2.6.3
>
>
> 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)
