we can't handle composite transports within composite transports - as
randomize is false, failover will walk the urls in order
On 2 Dec 2008, at 13:48, yinghe0101 wrote:
failover://(tcp://primary:61616,tcp://secondary:61616)?
randomize=false&maxReconnectAttempts=10
will work. I tried before. What I intend to configure is to have a
primary
group of brokers and a secondary group of brokers, both group are
using
failover, so:
failover://(failover://(tcp://primarygroup-broker1:61616,
tcp://primarygroup-broker2:61616)?
randomize=false&maxReconnectAttempts=50,
failover://(tcp://secondarygroup-broker1:61616,
tcp://secondarygroup-broker2:61616)?
randomize=false&maxReconnectAttempts=10)?randomize=false
is it possible to configure the above? I know the above gives me
exception
of invalid broker url.
best,
ying
rajdavies wrote:
Try:
failover://(tcp://primary:61616,tcp://secondary:61616)?
randomize=false&maxReconnectAttempts=10
On 2 Dec 2008, at 00:09, yinghe0101 wrote:
hi,
Can I do the configure the following activemq url on the client
side?
failover://(failover://(tcp://primary:61616,tcp://secondary:61616)?
randomize=false&maxReconnectAttempts=10,
failover://(tcp://primary:61616,tcp://secondary:61616)?
randomize=false&maxReconnectAttempts=10)?randomize=false
It gives me Invalid broker url exception thrown by new
URI(brokerURL). Is
there any way I can achieve the above semantic? what is the syntax?
Thanks
best,
Ying
--
View this message in context:
http://www.nabble.com/failover-URI-tp20783475p20783475.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
--
View this message in context:
http://www.nabble.com/failover-URI-tp20783475p20792524.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
