[rabbitmq-discuss] RabbitMQ windows service says it's started when it isn't ready

Robert Raschke rtrlists at googlemail.com
Mon Mar 24 15:50:44 GMT 2014

Hi Mat,

this is a consequence of how the Windows Service is started. The erlsrv.exe
reports back to Windows when Erlang has been started. But this in no way
means that the application running in the Erlang VM has also finished

Incidentally, this is the way a lot of systems start up. JBoss startup has
the exact same issue. Although calling it an issue is debatable :-)

Two ways forward are: 1. Application level interface that allows you to
query if your system is up and open for business. 2. Put sleeps into the
startup sequence, which appears to be a common remedy, unfortunately. 3.
Ignore errors on startup and retry until stable.

Hope this helps,
 I'm using RabbitMQ 3.2.1, Erlang R16B02

The issue described in the subject causes problems for other services which
depend on RabbitMQ

For instance if I have windows service X which has a dependency configured
for the RabbitMQ windows service then when I start X the RabbitMQ service
will be started first

However the RabbitMQ service reports that it's started before it's ready to
accept connections

Hence when service X tries to start it finds it cannot connect to RabbitMQ

This is mostly a problem when the machine is restarted as the services
which depend on RabbitMQ may fail to start

Is this a bug in RabbitMQ's windows service? Is there any way to allow
dependencies to work?

Any other suggestion also welcome, although I really want to avoid the
equivalent of sleeps

Mat B

rabbitmq-discuss mailing list
rabbitmq-discuss at lists.rabbitmq.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140324/d7c01c86/attachment.html>

More information about the rabbitmq-discuss mailing list