[rabbitmq-discuss] Pika IOLoop issue
zedhm at yahoo.co.uk
Thu Oct 20 17:11:51 BST 2011
Hi Gavin, I do not have a trace and this is not an easy issue to trigger but I think I have understood what is going on. This issue happens, in my case, when the connection drops and Pika handles the error. This results in the on_connection_closed callback getting called which I have instructed to stop the connection.ioloop. I think the problem is that if you have a nested poll()s you end up with nested handlers so even if the poller (i.e. the while loop in poller.start())is stopped, when the call stack unwinds you can end up with calls to poll() getting executed as a result of a transport.rpc(). Does this make any sense?
From: Gavin M. Roy <gmr at myyearbook.com>
To: E Hope-Morley <zedhm at yahoo.co.uk>
Cc: "rabbitmq-discuss at lists.rabbitmq.com" <rabbitmq-discuss at lists.rabbitmq.com>
Sent: Thursday, 20 October 2011, 14:29
Subject: Re: [rabbitmq-discuss] Pika IOLoop issue
That is peculiar. What is the duration of time between the stop and pending event? Is an exception being thrown? Do you have a traceback?
On Thursday, October 20, 2011 at 12:55 PM, E Hope-Morley wrote:
> I am using Pika on Ubuntu 11.04. When I call SelectConnection.ioloop.stop() following a connection drop on my connection, it sometimes fails to actually stop the ioloop i.e. following the call to stop(), a callback may sometimes be called in response to a pending event. Any ideas?
>rabbitmq-discuss mailing list
>rabbitmq-discuss at lists.rabbitmq.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss