Hello Gordon! I've seen reconnection working, I haven't tried URL lists, and I hadn't seen mention of resending unconfirmed messages. I'll look at both of those now, and thanks for the pointer! We've moved to the messaging API already, so this may make a great short term solution for us...
On Wed, May 5, 2010 at 2:31 PM, Gordon Sim <g...@redhat.com> wrote: > On 05/05/2010 08:22 PM, Kerry Bonin wrote: >> >> I like the idea of generalizing the failover scheme. Any suggestions >> on where to start? An externally configurable list of brokers >> published to amq.failover would seem an appropriate first step, and >> then work on mechanisms to update those lists. I'm looking over >> failover examples now... > > The messaging api in c++ and python both support reconnection and can take a > list of urls to try. They will replay any unconfirmed messages on reconnect > as well. So if your overall solution doesn't require actual message > replication, this may work for you. > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:dev-subscr...@qpid.apache.org > > --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
