[rabbitmq-discuss] Temporary queue being made when task fails

Ask Solem ask at rabbitmq.com
Mon Aug 22 16:52:57 BST 2011

On 22 Aug 2011, at 16:36, Matthias Radestock wrote:

> Mark,
> On 22/08/11 15:42, Mark Steele wrote:
>> Incidentally, I have also seen this behavior (where autodelete queues
>> don't get deleted). I'm assuming it's a bug.
> Have you seen this in the context of celery or in general?
> I am not aware of any problems with auto-delete queues in Rabbit.

Note that auto_delete queues are not deleted until the last consumer
stops consuming from it, and an auto_delete queue is *not*
deleted if there have never been any consumers consuming from it.

This is what the x-expires argument to queue_declare was meant to solve:

x-expires is supported by Celery, but not disabled by default as it
was first introduced in RabbitMQ 2.1.0 (which considering that it is
quite some time ago now, it can probably be enabled by default soon).

More information about the rabbitmq-discuss mailing list