[rabbitmq-discuss] CRITICAL:pika.connection:Attempted to send frame when closed
Michael Klishin
mklishin at gopivotal.com
Tue May 27 13:11:28 BST 2014
On 27 May 2014 at 15:37:01, shilpa karkera (shilpa.karkera at finoux.com) wrote:
> > The RabbitMQ producer and consumer for a particular queue stops
> producing and consuming completely when such a warning occurs.
> It is understood that the message bytes running over the buffer
> is overwhelmed, and thus it might cause this issue.
>
> However, the question is, Why doesn't the consumer release the
> message in the buffer once it consumes this message initially,
> instead it accumulates in the buffer. This is what I have researched
> and understood regarding the above issue. Kindly help troubleshoot!
I'm pretty sure the issue has little to do with buffers. More likely you're trying to
use an AMQP 0-9-1 connection that's already closed, either because of a network problem or
something else.
Please post RabbitMQ log and full stack trace from Pika.
--
MK
Software Engineer, Pivotal/RabbitMQ
More information about the rabbitmq-discuss
mailing list