[rabbitmq-discuss] RabbitMQ blocking issue

Thu Feb 21 17:36:17 GMT 2013

Hi Matthias,

Yes, the connection did resume after toggling the vm_memory_high_watermark.

Since the messages are sent in a burst and I can see the connection going into flow-control, I think it might be possible we are hitting the edge case you described.  We are using Spring-AMQP to perform the publishing.

Dan

-----Original Message-----
From: Matthias Radestock [mailto:matthias at rabbitmq.com] 
Sent: Thursday, February 21, 2013 12:26 PM
To: Konar Peter (Nokia-LC/Chicago)
Cc: Daniel Buchko; Carroll James (Nokia-LC/Malvern); Hancock Craig (Nokia-LC/Chicago); Venus Justin (Nokia-LC/Chicago); Yu Jerry.3 (Nokia-LC/Alpharetta); Lieber Dick (Nokia-LC/Chicago); Johnson Anthony (Nokia-LC/Alpharetta); Mccuiston Mitchell (Nokia-LC/Chicago); rabbitmq-discuss at lists.rabbitmq.com
Subject: Re: [rabbitmq-discuss] RabbitMQ blocking issue

Peter,

On 21/02/13 16:25, Konar Peter (Nokia-LC/Chicago) wrote:
>    Latest attempts:

Excellent. Exactly what I wanted to see. Or rather not. It does look like rabbit has forgotten to read from the connection :(

Did the connection resume work after the vm_memory_high_watermark toggling?

After staring at the code for a couple of days I have identified and fixed one scenarios in which a connection could end up in the state you are seeing. It happens only after an illegal sequence of channel.close followed by basic.publish on the same channel, and only during a very narrow window in conjunction with flow control. So I doubt this is the cause, but it would still be worth giving that fix a try, just to rule out that scenario. I will send you a patch by private email.

Regards,

Matthias.