activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nakarikanti, Nageswara" <NNakarika...@dwd.IN.gov>
Subject RE: Failover, how does it work?
Date Mon, 28 Mar 2011 22:06:13 GMT
And, adding  my question...

When Master Broker goes down, is there any way that administrators get a notification(e-mail
etc...) that it went down.

Should Only a "manual" restart to bring it up again?


Thank You,
Nag.



-----Original Message-----
From: Timothy Bish [mailto:tabish121@gmail.com] 
Sent: Thursday, March 24, 2011 10:32 AM
To: users@activemq.apache.org
Subject: Re: Failover, how does it work?

On Thu, 2011-03-24 at 13:27 +0100, Oscar Pernas wrote:
> Hi all (again),
> 
> 
> Im trying to understand well, how the failover transport works. I know 
> that if you have an active-pasive architecture and your active broker 
> goes down, all messages are send to the pasive broker. But, for 
> example, if we have a machine that have configured an active-pasive 
> brokers configuration like
> this:
> 
> failover://(tcp://localhost:61616,localhost2:61616)?randomize=false
> 
> If you remove the ethernet network cable, this machine couldnt connect 
> to any broker, but if I plug-in the cable again, to which broker the 
> connection will be stablished? if is developed like a pooling, could 
> really happen that this machine connect to the pasive broker instead to the first one?
> 
> If this could happen, what is the usual way to change this machine to 
> the active? Im using activemq-cpp.

The slave broker won't accept connections until it becomes the master so the client won't
connect to a slave.  It will just keep moving through the list of URI's attempting to connect
until a broker becomes available.

Regards

--
Tim Bish
------------
FuseSource
Email: tim.bish@fusesource.com
Web: http://fusesource.com
Twitter: tabish121
Blog: http://timbish.blogspot.com/



Mime
View raw message