Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@qpid.apache.org
Received-SPF: pass (nike.apache.org: local policy)
From: Kapil Dhawan <Kapil.Dhawan@tecnotree.com>
To: "users@qpid.apache.org" <users@qpid.apache.org>
Date: Thu, 11 Feb 2010 21:17:10 +0200
Subject: RE: Switching listener to the secondary broker
Thread-Topic: Switching listener to the secondary broker
Thread-Index: AcqrS5Y1QvyPaaxpSYOt3eYesiaPXQAAv1iQ
Message-ID: <960996F6EFBCB843BFD62DAA96BD1DD8182E2F7D67@esmail10>
References: <960996F6EFBCB843BFD62DAA96BD1DD8182E2F7517@esmail10>
	 <b9472b591002110137p793c208ep35d72004e667836e@mail.gmail.com>
	 <960996F6EFBCB843BFD62DAA96BD1DD8182E2F7B6C@esmail10>
 <f5f5e0731002111053h265d6de0t807fe00ca04b1d73@mail.gmail.com>
In-Reply-To: <f5f5e0731002111053h265d6de0t807fe00ca04b1d73@mail.gmail.com>
Accept-Language: en-US, fi-FI
Content-Language: en-US
acceptlanguage: en-US, fi-FI
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi Rajith,

We are using C++ client.

Oh thanks to mention that failover is with client. Got my answer.

I will be using C++ broker and C++ client and will setup IP Address / Port =
for all brokers in client side API.

Regards
Kapil Dhawan

-----Original Message-----
From: Rajith Attapattu [mailto:rajith77@gmail.com]=20
Sent: Friday, February 12, 2010 12:24 AM
To: users@qpid.apache.org
Subject: Re: Switching listener to the secondary broker

What client are you using?
The JMS client, the c++ client (and I believe the python client)  all
support failover.
Failover is a facility provided from the client side not the broker.

You can use either the C++ broker or the Java broker.
The c++ broker supports clustering while the java broker currently does not=
.
Therefore unless persistence is used, all transient messages on the
Java broker instance that went down will be lost.
For some use cases this might be acceptable. Therefore which broker to
use depends on your use case.

Rajith

On Thu, Feb 11, 2010 at 7:06 AM, Kapil Dhawan
<Kapil.Dhawan@tecnotree.com> wrote:
> Thanks Marnie.
>
> We are using C++ broker but we are open to use Java broker as well.
>
> Regards
> Kapil
>
> -----Original Message-----
> From: Marnie McCormack [mailto:marnie.mccormack@googlemail.com]
> Sent: Thursday, February 11, 2010 3:07 PM
> To: users@qpid.apache.org
> Subject: Re: Switching listener to the secondary broker
>
> Hi Kapil,
>
> Are you using the Java or C++ broker ?
>
> For the Java Broker, detailed of how to use failover (automated for the
> client) are available here:
> http://qpid.apache.org/connection-url-format.html
>
> Regards,
> Marnie
>
> On Thu, Feb 11, 2010 at 6:07 AM, Kapil Dhawan <Kapil.Dhawan@tecnotree.com=
>wrote:
>
>> Hi List,
>>
>> Is there any automated way of switching the listener to the secondary
>> broker in case primary broker is down.
>>
>>
>> - =A0 =A0 =A0 =A0 =A0Kapil
>>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: =A0 =A0 =A0http://qpid.apache.org
> Use/Interact: mailto:users-subscribe@qpid.apache.org
>
>


--=20
Regards,

Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org