[rabbitmq-discuss] Temporary queue being made when task fails
msteele at beringmedia.com
Mon Aug 22 18:47:13 BST 2011
This was not in the context of celery. One of our applications creates
an auto_delete non-durable private queue and binds it to an exchange.
Every once in a while (let's call it once every quarter or so) we've
observed that if communication is broken (network issue, cable
unplugged, etc...) the client disconnects (and restarts), however the
queue remains there forever until manually deleted, accumulating
messages. To finally get it to be deleted, we have to do a
`rabbitmqctl close_connection` with the pid.
If I remember correctly, the server is aware that there is no clients
connected to the queue, however it doesn't delete it for some reason.
Next time it happens, I'll post more details. I suspect it's somehow
related to an unclean connection teardown and/or ssl.
On Mon, Aug 22, 2011 at 11:36 AM, Matthias Radestock
<matthias at rabbitmq.com> wrote:
> 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.
More information about the rabbitmq-discuss