[
https://issues.apache.org/jira/browse/ARTEMIS-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17153693#comment-17153693
]
ASF subversion and git services commented on ARTEMIS-2835:
----------------------------------------------------------
Commit 6f8ff55dec629504d34b7dd3757bff24fa16c575 in activemq-artemis's branch
refs/heads/master from Howard Gao
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=6f8ff55 ]
ARTEMIS-2835 Porting HORNETQ-1575 and HORNETQ-1578
1 of 2) - Porting of HORNETMQ-1575
In a live-backup scenario, when live is down and backup becomes live, clients
using HA Connection Factories can failover automatically. However if a
client decides to create a new connection by itself (as in camel jms case)
there is a chance that the new connection is pointing to the dead live
and the connection won't be successful. The reason is that if the old
connection is gone the backup will not get a chance to announce itself
back to client so it fails on initial connection.
The fix is to let CF remember the old topology and use it on any
initial connection attempts.
> Porting HORNETQ-1575 and HORNETQ-1578
> -------------------------------------
>
> Key: ARTEMIS-2835
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2835
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.13.0
> Reporter: Howard Gao
> Assignee: Howard Gao
> Priority: Major
> Fix For: 2.14.0
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> The HORNETQ-1575 and HORNETQ-1578 bug fixes are not available in Artemis. It
> could be hit by users in Artemis too.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
