qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kapil Dhawan <Kapil.Dha...@tecnotree.com>
Subject RE: Switching listener to the secondary broker
Date Thu, 11 Feb 2010 19:29:36 GMT
Thanks for being so helpful and prompt.

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

On Thu, Feb 11, 2010 at 2:17 PM, Kapil Dhawan
<Kapil.Dhawan@tecnotree.com> wrote:
> Hi Rajith,
>
> We are using C++ client.
>
> Oh thanks to mention that failover is with client. Got my answer.
YW.

> I will be using C++ broker and C++ client and will setup IP Address / Port for all brokers
in client side API.
Great. Please don't hesitate to ask any questions if you need further help.

> Regards
> Kapil Dhawan
>
> -----Original Message-----
> From: Rajith Attapattu [mailto:rajith77@gmail.com]
> 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.
>>>
>>>
>>> -          Kapil
>>>
>>
>> ---------------------------------------------------------------------
>> Apache Qpid - AMQP Messaging Implementation
>> Project:      http://qpid.apache.org
>> Use/Interact: mailto:users-subscribe@qpid.apache.org
>>
>>
>
>
>
> --
> 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
>
>



-- 
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


Mime
View raw message