Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <6C2A0E83E07BAA48A34BAE8F5419AF27FEBCF2F7C7@IOTMVSP01VW.shared.state.in.us>
References: <AANLkTimjBkMbdT_EvsaKc0YmC3FjX40JOvT0Si-CBf9m@mail.gmail.com>
 <1300977139.2773.1.camel@office>
 <6C2A0E83E07BAA48A34BAE8F5419AF27FEBCF2F7C7@IOTMVSP01VW.shared.state.in.us>
From: Oscar Pernas <oscar@pernas.es>
Date: Tue, 29 Mar 2011 14:22:47 +0200
Message-ID: <AANLkTi=hNZ1o3MsyUg1mCQEZnN+XShhRYd+y+M3gG05h@mail.gmail.com>
Subject: Re: Failover, how does it work?
To: users@activemq.apache.org
Cc: "Nakarikanti, Nageswara" <NNakarikanti@dwd.in.gov>
Content-Type: multipart/alternative; boundary=001485f20c1a646160049f9e1f72

--001485f20c1a646160049f9e1f72
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

To send email or notification we are thinking in use a monitorization tool
like nagios or something more light...

About the manual restart, i think that you could take a look about
linux-heartbeat v2, you could configure services to monitorize and make
petitions.


One more question, If we have a cluster, if the master goes down, all
messages goes to the slave, but, if we start the master again, all messages
will send to the master again?

2011/3/29 Nakarikanti, Nageswara <NNakarikanti@dwd.in.gov>

> 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=3Dfalse
> >
> > 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 th=
e
> 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/
>
>
>


--=20
=D3scar Pernas Plaza.

--001485f20c1a646160049f9e1f72--