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 <[email protected]> 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:[email protected]] > Sent: Thursday, February 11, 2010 3:07 PM > To: [email protected] > 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 > <[email protected]>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:[email protected] > > -- Regards, Rajith Attapattu Red Hat http://rajith.2rlabs.com/ --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
