activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ken.mccracken" <ken.mccrac...@gmail.com>
Subject FailoverTransport rebinding to master
Date Mon, 20 Dec 2010 18:00:26 GMT

Hi,

I'm using the FailoverTransport via the following config:
failover:(tcp://primary:61616,tcp://secondary:61616)?randomize=false

My question is, if I bring up two ActiveMQ servers at primary and secondary,
and they are both up, messages will be produced to the primary.  When the
primary goes down, messages will be send to the secondary.  When the primary
comes back online, messages continue to be sent to the secondary.  Is there
a way to make it "rebind" to the primary, or check if primary is again
available every 5 minutes or so?  

The reason is that I want to use my ActiveMQ cluster in an active-active
setup with multiple hosts distributed to multiple ActiveMQs.  When one
ActiveMQ goes down, traffic should switch to the other; when that ActiveMQ
is brought back online, traffic should again re-distribute.

Should I use a different Transport?  Do I need to write my own to have this
behavior?

Thanks!
-Ken McCracken

-- 
View this message in context: http://activemq.2283324.n4.nabble.com/FailoverTransport-rebinding-to-master-tp3095911p3095911.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Mime
View raw message