[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-users
Subject:    Re: FailoverTransport rebinding to master
From:       Dejan Bosanac <dejan () nighttale ! net>
Date:       2010-12-21 9:44:16
Message-ID: AANLkTi=puHLXJN1=Kk-ptMVAXd_7hV8McBiBJiF2G2XW () mail ! gmail ! com
[Download RAW message or body]

Hi Ken,

we don't have this feature at the moment. You can raise a feature
request in Jira (and take a stab at implementing it).

Cheers
--
Dejan Bosanac
-----------------
FuseSource - The experts in open source integration and messaging.
Email: dejanb@fusesource.com
Web: http://fusesource.com
Twitter:  http://twitter.com/dejanb
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net



On Mon, Dec 20, 2010 at 7:00 PM, ken.mccracken <ken.mccracken@gmail.com> wrote:
> 
> 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.
> 


[prev in list] [next in list] [prev in thread] [next in thread]