-
Notifications
You must be signed in to change notification settings - Fork 8
Description
When we start the service on windows, the startup is complete in a second. But looking at the log files we can see that it takes it much longer to be ready to accept connections (in my observation, around 40 seconds when the system boots and around 12 seconds when starting from the Services console).
As a result of such behavior, any other service depending on RabbitMQ service will fail to start during the system startup.
Suppose, ServiceA depends on RabbitMQ and makes a connection to the local RabbitMQ node. Both services are configured to start automatically.
Windows will first start RabbitMQ service, wait for it to report the "started" state, then start ServiceA.
ServiceA will try to connect to RabbitMQ node and will fail, because RabbitMQ service does not accept connections yet.