[rabbitmq-discuss] 505 UNEXPECTED_FRAME when publishing in a consume handler using pika

Brian Lalor blalor at bravo5.org
Mon Dec 12 11:30:16 GMT 2011

On Dec 12, 2011, at 6:27 AM, Simon MacMullen wrote:

> I'm not a Pika expert, but that error message is triggered by wrongly interleaved frames on a *single* channel - the most likely cause is using a single channel from multiple threads in a client where channels are not threadsafe (I suspect Pika is such a client).

Thanks, Simon.  Pika is definitely not thread-safe (and the clients I've written to this point have used multiple threads and connections, which feels ugly).  The thing is, all *three* channels close at once.  I suspect a Pika bug…

More information about the rabbitmq-discuss mailing list