You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2019/03/11 12:49:00 UTC

[jira] [Created] (AMQ-7165) failover transport and rebalanceClusterClients=true should fall back to original broker list if no broker on updated cluster information is available

Gary Tully created AMQ-7165:
-------------------------------

             Summary: failover transport and rebalanceClusterClients=true should fall back to original broker list if no broker on updated cluster information is available
                 Key: AMQ-7165
                 URL: https://issues.apache.org/jira/browse/AMQ-7165
             Project: ActiveMQ
          Issue Type: Bug
          Components: JMS client
    Affects Versions: 5.15.0
            Reporter: Gary Tully
            Assignee: Gary Tully
             Fix For: 5.16.0


The failover transport updates list takes full precedence, but results in the existing static information being ignored. Because the rebalance information is based on the presence of network bridges, when the bridge is down, the information can be a subset of reality, leaving a client using less information than was statically configured.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)