[rabbitmq-discuss] Pika 0.9.5 KeyError: Tx.SelectOk
mpietrek at skytap.com
Wed Mar 14 22:34:13 GMT 2012
Cool, and thanks. Just wanted to make sure you knew about it in case it
hadn't been seen before.
On Wed, Mar 14, 2012 at 1:52 PM, Gavin M. Roy <gmr at myyearbook.com> wrote:
> Hi Matt,
> I'll have to go back through and look at the fixed bugs. I know I've
> applied a fair amount of fixes to BlockingConnection, I'd not be surprised
> if this was one of them. There is a known blocker in Github master right
> now, but I expect to see 0.9.6 drop "real soon"
> Feel free to check the issues list at http://github.com/pika/pika
> On Wednesday, March 14, 2012 at 4:40 PM, Matt Pietrek wrote:
> I'm experiencing a KeyError exception, where the key is "Tx.SelectOk" when
> using Pika 0.9.5.
> The scenario: A simple program that simply writes two messages a second to
> a queue. While this test is running, I stop the broker, then restart it a
> few seconds later. I explicitly check for AMQPConnectionError exceptions,
> and if seen reconnect to the broker. About half the time, the test works as
> intended. However, other times I see the KeyError exception, which my guess
> is not what's intended.
> My writing code looks like this:
> channel = self._channel
> except AMQPConnectionError as e:
> Digging into the traceback data, the faulting line is in
> Pika's blocking_connection.py:rpc()
> # Find our reply in our list of replies
> for reply in self._replies:
> if reply in replies:
> * frame = self._frames[reply] # THIS HERE IS THE LINE*
> self._received_response = True
> if callback:
> return frame
> Known issue? Expected and acceptable? Thoughts?
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss