[rabbitmq-discuss] Exclusive queues and delete-on-disconnect

[Garrett Smith]

My understanding is that declaring a queue as exclusive will cause the
queue to be deleted as soon as the declaring channel (or connection?)
is closed.

I've observed cases when a channel/connection has not been closed
cleanly (e.g. sudden network failure) and the queue is not deleted.
(If this is unintended behavior, I can try to consistently recreate
the problem. It may be the case that this behavior is intermittent).

When the consumer re-declares (e.g. on restart), the broker complains
about an exclusive queue already existing. The fix I'm using is to
manually delete the queue.

Are there any suggestions for dealing with this? Apart from the added
complexity of restarting the consumer, I'm concerned that messages
will pile up in the queue with on one to consume them.

Garrett