failover transport and rebalanceClusterClients=true should fall back to original broker list if no broker on updated cluster information is available.

Solution Verified - Updated -

Issue

  • When using a broker configuration with rebalanceClusterClients=true and updateClusterClients=true, the client side failover transport should fall back to the original broker list (as specified in the failover: transport URL) if it fails to connect to any of the broker URLs it received as part of the broker cluster update.

  • Currently the failover transport only tries to reconnect to those broker URLs that it received as part of a cluster update (ConnectionControl message) from the connected broker.

Environment

  • Red Hat AMQ
    • 6.3.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In