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 <manuel.chi...@adilamtech.com.au>wrote: > 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://activemq.2283324.n4.nabble.com/Failover-all-clients-to-same-secondary-broker-tp4680171p4680650.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
