Cool, and thanks. Just wanted to make sure you knew about it in case it hadn't been seen before.<br><br>Matt<br><br><div class="gmail_quote">On Wed, Mar 14, 2012 at 1:52 PM, Gavin M. Roy <span dir="ltr"><<a href="mailto:gmr@myyearbook.com">gmr@myyearbook.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
Hi Matt,�</div><div><br></div><div>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"</div>
<div><br></div><div>Feel free to check the issues list at <a href="http://github.com/pika/pika" target="_blank">http://github.com/pika/pika</a></div><div><br></div><div>Gavin</div><div><div class="h5">
<div></div>
<p style="color:#a0a0a8">On Wednesday, March 14, 2012 at 4:40 PM, Matt Pietrek wrote:</p>
</div></div><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px">
<span><div><div><div class="h5"><div><div>I'm experiencing a KeyError exception, where the key is "Tx.SelectOk" when using Pika 0.9.5.</div><div><br></div><div>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.</div>
<div><br></div><div>My writing code looks like this:</div><div><div><div>� � � � � � try:</div><div>� � � � � � � � channel = self._channel</div><div>� � � � � � � � channel.tx_select()</div><div>� � � � � � � � channel.basic_publish(exchange='',</div>
<div>� � � � � � � � � � routing_key=queue_name,</div><div>� � � � � � � � � � body=json_string,</div><div>� � � � � � � � � � properties=pika.BasicProperties(delivery_mode=2))</div><div>� � � � � � � � channel.tx_commit()</div>
<div>� � � � � � � � return</div><div>� � � � � � except AMQPConnectionError as e:</div><div>� � � � � � � � self._reconnect()</div></div></div><div><br></div><div>Digging into the traceback data, the faulting line is in Pika's�blocking_connection.py:rpc()</div>
<div><br></div><div><div>� � � � # Find our reply in our list of replies</div><div>� � � � for reply in self._replies:</div><div>� � � � � � if reply in replies:</div><div><b><u>� � � � � � � � frame = self._frames[reply] # THIS HERE IS THE LINE</u></b></div>
<div>� � � � � � � � self._received_response = True</div><div>� � � � � � � � if callback:</div><div>� � � � � � � � � � callback(frame)</div><div>� � � � � � � � del(self._frames[reply])</div><div>� � � � � � � � return frame</div>
</div><div><br></div><div>Known issue? Expected and acceptable? Thoughts?</div><div><br></div><div>Thanks,</div><div><br></div><div>Matt</div>
</div></div></div><div><div>_______________________________________________</div><div>rabbitmq-discuss mailing list</div><div><a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.rabbitmq.com</a></div>
<div><a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a></div></div></div></span>
</blockquote>
<div>
<br>
</div>
</blockquote></div><br>