[rabbitmq-discuss] RabbitMQ blocking issue

[Matthias Radestock]

Peter,

On 20/02/13 21:54, Konar Peter (Nokia-LC/Chicago) wrote:
> I have attached two logs that show issues with in the first 5 minutes
> of it happening.

These reports show two connections with a non-empty Recv-Q at the server 
side, a non-empty Send-Q at the client side, and a connection state of 
'running' in rabbit. And it looks like there was no change in that 
situation over at least five minutes. The connections were terminated by 
rabbit ~30 minutes later due to missing heartbeats.

This all points towards rabbit having stopped reading from the socket 
even though it thinks it is.

Needless to say that is rather worrying, and not something we have ever 
encountered before.

In order to investigate this further...

- Please upgrade Erlang to R15B03. It is conceivable that the issue is 
caused by bugs in the Erlang VM that have since has been fixed.

- Next time the issue occurs, please run
   rabbitmqctl set_vm_memory_high_watermark 0.0001
followed by
   rabbitmqctl set_vm_memory_high_watermark 0.4
and check whether that causes the stalled connections to resume working.


Regards,

Matthias.