[
https://issues.apache.org/jira/browse/ARTEMIS-1995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16564610#comment-16564610
]
ASF subversion and git services commented on ARTEMIS-1995:
----------------------------------------------------------
Commit 1282bebf3fca23faffa7379177540a8ae78d2830 in activemq-artemis's branch
refs/heads/2.6.x from [~gaohoward]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=1282beb ]
ARTEMIS-1995 Client fail over fails when live shut down too soon
In a live-backup scenario, if the live is restarted and shutdown too soon,
the client have a chance to fail on failover because it's internal topology
is inconsistent with the final status. The client keeps connecting to live
already shut down, never trying to connect to the backup.
It's a porting from HORNETQ-1572.
(cherry picked from commit 983232d27330515a50a3cdb9d7cd664ebf3ca6f2)
> Client fail over fails when live shut down too soon
> ---------------------------------------------------
>
> Key: ARTEMIS-1995
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1995
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.6.2
> Reporter: Howard Gao
> Assignee: Howard Gao
> Priority: Major
> Fix For: 2.6.3
>
>
> In a live-backup scenario, if the live is restarted and shutdown too soon,
> the client have a chance to fail on failover because it's internal topology
> is inconsistent with the final status. The client keeps connecting to live
> already shut down, never trying to connect to the backup.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
