[rabbitmq-discuss] AD Queues Not AutoDeleting

Chris stuff at moesel.net
Tue Apr 2 19:17:29 BST 2013

Thanks for the hint.  My concern with that is how it works with HA /
Failover.  In fact, it may be a concern for autodelete as well.

I'd like to have the concept of exclusive queues, but if the server goes
down and I have to reconnect to it again, or reconnect to another node in
the cluster (if HA policy mirrors queues), I assume it will not allow me to
resubscribe to the exclusive queue.  So... I will lose messages.

Or to put it another way:  I think that if I want to be sure not to lose
messages during a reconnection, I have to reconnect to the same queue, and
therefore that queue cannot be declared exclusive.  Which leads to the next
question: If it is declared autodelete, do I have a small grace period in
which I can reconnect and resubscribe before it autodeletes itself?

Thanks again!  You guys are awesome!

On Tue, Apr 2, 2013 at 9:41 AM, Michael Klishin <michael.s.klishin at gmail.com
> wrote:

> 2013/4/2 Matthias Radestock <matthias at rabbitmq.com>
>> Couldn't you simply declare the queues as 'exclusive' instead of
>> 'auto-delete'?
> Clarification: then it will always be removed when the connection that
> created it is closed
> --
> MK
> http://github.com/michaelklishin
> http://twitter.com/michaelklishin
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130402/762d08ec/attachment.htm>

More information about the rabbitmq-discuss mailing list