activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Tully <>
Subject Re: Using failover with updateClusterClients, which one has precedence?
Date Thu, 26 Oct 2017 10:55:08 GMT
yes, that is the intent. The broker makes the decision and when it does
round robin or random there should be a reasonable distribution. The issue
when it is left to clients is they can all behave the same - as in non
random random. With updateClusterClients the only random selection lives in
the broker and is shared by the ordered list being pushed to the clients.
There are url parameters to set on failover to have the client ignore that
if you like: reconnectSupported

On Wed, 25 Oct 2017 at 16:26 Devlin <> wrote:

> ActiveMQ 5.11
> When using failover URLs like this in a network of brokers where
> updateClusterClients=true, how is failover handled?
> failover:(tcp://hydra:61616,tcp://orion:61616,tcp://omega:61616,tcp://bigmoma:61616)?randomize=false
> The behavior we're seeing is that, upon initial connect, the first host
> (hydra) is selected, that's expected, but when the connection fails, the
> client randomly connects to another broker in the list, not the second host
> in the failover URL. So it appears updateClusterClients takes precedence
> over the order by which hosts are configured in the failover URL, is that a
> valid assumption?
> --
> Sent from:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message