[rabbitmq-discuss] Windows service recovery

Lior Barnea Barnea at 3i-mind.com
Mon May 28 08:09:23 BST 2012

Hi Emile,

This is part of the recovery testing we are conducting, this is not a real issue that we encountered but one produced on purpose...

Still, I would have expected that erlsrv could detected that erl.exe is already up when windows restarts it and re-attach to it instead of failing...

Best regards,

-----Original Message-----
From: Emile Joubert [mailto:emile at rabbitmq.com] 
Sent: Friday, May 25, 2012 17:59
To: Lior Barnea
Cc: rabbitmq-discuss at lists.rabbitmq.com
Subject: Re: [rabbitmq-discuss] Windows service recovery

Hi Lior,

On 23/05/12 15:37, Lior Barnea wrote:
> Killing erlsvr.exe does not stop erl.exe (meaning rabbitMQ still
> running) but does alert windows that then tries to restart erlsvr.exe
> When erlsvr.exe is started again, it tries to spawn erl.exe again and 
> fails because it is already running, failing erlsvr.exe completely, 
> recovery failed.

I can confirm that your description is accurate. erlsrv acts as an interface between the Windows service management and the Erlang process.
It can communicate failures of the broker to Windows but it does not cope if erlsrv itself fails. The design is presumably based on the estimate that the broker is far more likely to fail.

Are you exploring a hypothetical concern or is this a real issue that is preventing you from deploying and using the broker?


More information about the rabbitmq-discuss mailing list