[
https://issues.apache.org/jira/browse/AMQ-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13986565#comment-13986565
]
Gary Tully commented on AMQ-4812:
---------------------------------
It may be sorted with https://issues.apache.org/jira/browse/AMQ-4505
The idea of sticking with the first in the updated list is because that ordered
list is provided by the broker, and will be different for each connection,
allowing the broker to dictate the rebalance.
Maybe make a variant of
https://github.com/apache/activemq/blob/20f384ce59b758a0f3c1b0e0620e2efd58ca230a/activemq-unit-tests/src/test/java/org/apache/activemq/transport/failover/FailoverComplexClusterTest.java
to check your usecase.
On the rule that does not allow a message to replay back to the broker where it
came from. there is a policy that can control that
see: http://activemq.apache.org/networks-of-brokers.html -
conditionalNetworkBridgeFilterFactory
> Rebalance not working on 5.8.0
> ------------------------------
>
> Key: AMQ-4812
> URL: https://issues.apache.org/jira/browse/AMQ-4812
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 5.8.0
> Reporter: Wayne Evans
> Attachments: (Example)IsecStateConsumer.properties,
> Broker1_activemq.xml, Broker2_activemq.xml
>
>
> Two brokers networked.
> Transport connectors configured on both with:
> rebalanceClusterClients="true" updateClusterClients="true"
> updateClusterClientsOnRemove="true"
> Clients configured with only Broker 1 in Failover string.
> Clients all connect to 1st Broker when starting up.
> When first broker is stopped all clients fail over to 2nd Broker.
> When 1st Broker is brought back up all clients remain on 2nd Broker.
> Config files from both Brokers and one sample client config attached.
> Related issue - queued messages on 1st Broker that were passed from 2nd
> broker initially are not consumed after 1st Broker is brought back up as
> rules prevent them from being passed back to 2nd Broker where client
> consumers are attached.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
