[rabbitmq-discuss] exceptions on fast opening a number of connections / exception on TCP connection

Marek Majkowski majek04 at gmail.com
Wed Feb 9 09:11:33 GMT 2011

On Tue, Feb 8, 2011 at 19:26, Taek Joo Kim <taicki at gmail.com> wrote:
> Actually I saw this log message and am trying to debug. In our case, I
> did not get any exceptions on the client side.
> Could I ask what the cause is? Does the broken framing mean pika's issue?

It is caused by using one pika connection or channel in multiple threads.
Pika is not multithreaded.


> On Mon, Feb 7, 2011 at 2:00 PM, Marek Majkowski <majek04 at gmail.com> wrote:
>> On Sat, Jan 29, 2011 at 18:18, Marcin Krol <mrkafk at gmail.com> wrote:
>> > I wrote a "stress test" function that (relatively) quickly does the
>> > following: it creates a number of threads that open a new connection to
>> > Rabbit, do RPC call over Rabbit, close the connection, sleep some
>> > milliseconds and iterate again.
>> >
>> > I'm getting following exceptions in Rabbit log:
>> >
>> > =ERROR REPORT==== 29-Jan-2011::18:06:04 ===
>> > exception on TCP connection <0.22244.4> from
>> > {inet_error,enomem}
>> For a record, this error is triggered by a broken framing. For example:
>> echo -e "AMQP\x00\x00\x09\x01AMQP\x00\x00\x09\x01"|nc localhost 5672

More information about the rabbitmq-discuss mailing list