[rabbitmq-discuss] Unexplained shutdown of RabbitMQ

Matthew Sackman matthew at lshift.net
Fri May 14 13:04:31 BST 2010

Hi Jason,

Thanks for the report, and all the details.

On Fri, May 14, 2010 at 01:44:43PM +0200, Jason Zaugg wrote:
> =System Details:=
> Erlang .572
> RabbitMQ 1.6.0
> Windows Server 2003 64Bit
> 8 core machine.
> Lots of free disk space.
> =Questions=
> 1. Can we configure RabbitMQ to suppress logging of the message queue
> when this error occurs. The log files are growing to 4GB+, and it's
> tricky to follow them.

Unfortunately not. We would like to fix that ourselves too and there's
meant to be a hook to be able to control that but there've been reports
that there've been bugs in Erlang itself regarding that particular hook.
It might be something we will be able to fix eventually.

> 2. What might "writer,send_failed,badarg" as the termination reason
> suggest as the root cause?
> 3. Prior the the shutdown, what is the meaning of:
>   exception on TCP connection <0.2021.0> from
>   {timeout,running}
>   exception on TCP connection <0.1707.0> from
>   connection_closed_abruptly

We think that you have heartbeats turned on. Heartbeats are quite
unreliable under Windows, especially when the machine is loaded, because
of schedular issues. Try turning heartbeats off (has to be done from
each client). In later releases of Rabbit (and its clients), we disabled
heartbeats by default. 1.6.0 is quite old - we'd recommend you upgrade
to 1.7.2 if you can.


More information about the rabbitmq-discuss mailing list