activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Torsten Mielke <tors...@fusesource.com>
Subject Re: AMQ 5.5.1 - Message Routing Doesn't Resume After Network Outage
Date Mon, 02 Apr 2012 07:20:00 GMT
> static:(failover:(tcp://hub1:61001,tcp://hub2:62001)?updateURIsSupported=false&amp;maxReconnectAttempts=1,failover:(tcp://hub2:61001,tcp://hub1:62001)?updateURIsSupported=false&amp;maxReconnectAttempts=1)

Hhm, if hub1 and hub2 are the same machines in both of the failover urls, then you only need
one of them, e.g. 

static:(failover:(tcp://hub1:61001,tcp://hub2:62001)?updateURIsSupported=false&amp;maxReconnectAttempts=1)

If however you want to connect to two different master/slave pairs from your broker instance,
then your url above is correct. I would just have named the latter pair hub3 and hub4 for
clarity. 

Hope that helps.

Torsten Mielke
torsten@fusesource.com
tmielke@blogspot.com




On Mar 30, 2012, at 6:35 PM, brucent wrote:

> Thanks.  I was simulating our more complicated production environment which
> uses hot standby instances.  I assume this would be the right URL to use for
> load balancing against two instances each with a hot standby?
> 
> static:(failover:(tcp://hub1:61001,tcp://hub2:62001)?updateURIsSupported=false&amp;maxReconnectAttempts=1,failover:(tcp://hub2:61001,tcp://hub1:62001)?updateURIsSupported=false&amp;maxReconnectAttempts=1)
> 
> Bruce
> 
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/AMQ-5-5-1-Message-Routing-Doesn-t-Resume-After-Network-Outage-tp4516807p4519600.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.





Mime
View raw message