[rabbitmq-discuss] Ghost consumers problem
Jose Ramon Palanco
jpalanco at gmail.com
Thu Jul 4 17:27:21 BST 2013
Thank you for your quick reponse. We only need one consumer per queue. We
already have AD (autodelete) and durable is setted to false. We tried
exclusive and non-exclusive. We still have ghost connections and consumers
even when the computers running the clients are powered off.
I read that it could be due the NAT, but I have reproduced the same issue
2013/7/4 Michael Klishin <michael.s.klishin at gmail.com>
> 2013/7/4 Jose Ramon Palanco <jpalanco at gmail.com>
>> 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 it because you have multiple connections using the queue?
> If you consumer from the queue, you can declare it as auto-delete and
> non-durable instead of exclusive. Then as soon as the last consumer
> (registered with basic.consume, not using basic.get) is gone, it will be
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss