[
https://issues.apache.org/jira/browse/ARTEMIS-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16349958#comment-16349958
]
ASF GitHub Bot commented on ARTEMIS-1654:
-----------------------------------------
GitHub user andytaylor opened a pull request:
https://github.com/apache/activemq-artemis/pull/1838
ARTEMIS-1654 - fix bridge reconnect logic
Make sure that if a bridge disconnects and there is no record in the
topology that it uses the original bridge connector to reconnect
https://issues.apache.org/jira/browse/ARTEMIS-1654
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/andytaylor/activemq-artemis ARTEMIS-1654
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/1838.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1838
----
commit 22311333dc19a6a76f377530b03f75eef5c186cc
Author: Andy Taylor <andy.tayls67@...>
Date: 2018-02-01T13:22:59Z
ARTEMIS-1654 - fix brige reconnect logic
Make sure that if a bridge disconnects and there is no record in the
topology that it uses the original bridge connector to reconnect
https://issues.apache.org/jira/browse/ARTEMIS-1654
----
> Bridge reconnect broken
> -----------------------
>
> Key: ARTEMIS-1654
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1654
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Andy Taylor
> Assignee: Andy Taylor
> Priority: Major
>
> A quorum fix broker this. Originally we used to leave a node in th etopology
> when it disconnected, this broke voting as all brokers thought a crashed live
> was still around. The bridge reconnect logic relied on this so now it needs
> to fall back to the originall connectors if no backup is available and the
> live is lost.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
