You could try something like DNS failover or a software loadbalancer
presenting a VIP, but the easiest way might be to change you app to handle
connecting to multiple brokers
On Tue, Apr 29, 2014 at 11:57 AM, mchinea
wrote:
> So it seems the only way to be sure clients are connected to either b
So it seems the only way to be sure clients are connected to either broker
reliably is to have one and only one of the brokers running and if/when it
fails, start running the broker in the second server so the clients can
switch to it. Is this correct?
--
View this message in context:
http://ac
That will not be a reliable solution. Anytime the failover transport is used
with more than one active broker, you can get clients connected to separate
brokers. Even without randomize, consider that a loss of connection due to
a network disconnect will cause the client to reconnect to a differen
