[rabbitmq-discuss] Auto-delete queues not compatible with basic.get (vs. basic.consume)?

Matt Pietrek mpietrek at skytap.com
Thu May 23 21:47:23 BST 2013

Thanks for the clarification Michael.

Another follow up question: What exactly is meant by "they can't be
shared"? Is the exclusivity limited to reading, or does it encompass both
reading and writing?

In my case, I'm constructing an RPC scenario. The queue I'm creating is for
the reply to come in on. Some other process using some other connection
must be able to write to it.

On Thu, May 23, 2013 at 1:38 PM, Michael Klishin <
michael.s.klishin at gmail.com> wrote:

> 2013/5/24 Matt Pietrek <mpietrek at skytap.com>
>> Eventually the code finishes and the connection goes away. The RabbitMQ
>> admin console shows no connections and no channels, but my queue was never
>> deleted.
> Auto-deleted queues are deleted the last consumer is cancelled or goes
> away. If there were no
> consumers at all, it won't be deleted.
> Exclusive queues will be deleted when
> the connection that created them is closed (but they also can't be shared).
> --
> 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/20130523/6a83c37b/attachment.htm>

More information about the rabbitmq-discuss mailing list