[rabbitmq-discuss] Reconnection strategies in Pika
Gavin M. Roy
gmr at myyearbook.com
Tue Jul 26 22:08:27 BST 2011
I'll take a look at that soon. As a work-around you can register with the callback manager to be notified when the connection closes and handle it yourself.
Check out the connection.Connection class to see how to do that.
On Tuesday, July 26, 2011 at 5:06 PM, Alex Grönholm wrote:
> 26.07.2011 19:13, Gavin M. Roy kirjoitti:
> > On Tuesday, July 26, 2011 at 11:57 AM, Marek Majkowski wrote:
> > > On Tue, Jul 26, 2011 at 16:08, Gavin M. Roy <gmr at myyearbook.com (mailto:gmr at myyearbook.com)> wrote:
> > > > The SimpleReconnectionStrategy implementation was to on disconnect, have a
> > > > incrementally delayed attempt to reconnect to the broker. I believe there's
> > > > a ticket with this being broken in 0.9.5, I need to confirm that's the case.
> > >
> > > Stupid question: what happens after reconnection succeeds, is
> > > the user informed in any way? What happens to things
> > > waiting on basic_consume and such?
> > There is a callback mechanism in place the user can subscribe to, but it must be treated as a new connection, there is nothing automated but the reconnection.
> > No channels recreated, etc. The behavior of it should mirror the 0.5.2 behavior as of right now. Future direction hasn't been contemplated. I just need reconnection to work, but as of 0.9.5 it doesn't. Would be nice if it did. The callbacks will handle channel creation etc.
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com (mailto:rabbitmq-discuss at lists.rabbitmq.com)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss