[rabbitmq-discuss] Ghost consumers problem
Jose Ramon Palanco
jpalanco at gmail.com
Thu Jul 4 15:06:25 BST 2013
We have an rabbitmq installation and we use rabbitmq-c clients compiled for
microsoft windows and running as a service. Everything works fine, even we
have enabled encrypted communications using OpenSSL.
It turns out that we have a problem with ghost consumers and having read a
lot, we still come up with the solution.
The scenario is as follows:
Clients connect to the broker and everything works fine until Windows
restarts. To speedup system reboot, Microsoft doesn't give us a chance to
finish executing our tasks: so we can't closed session properly.
This implies that the queue remains alive with a ghost consumer.
After reboot, the service starts and when trying to create the queue, it
conflicts with the former queue. We tried to create the queue as exclusive,
but it doesn't allow us to connect because we haven't permission.
Is there a way to close the communications when a connection is not
stablished? Or in the worst case, there is a procedure to clean the queues
with ghost consumers?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss