Hrmmmm, you bring up a good point. A queue with this name definitely once had consumers. It looks like there were never any deliveries for the exact queue in question though. I'm thinking that the reconnect logic in the library I'm using is causing queues to be redeclared when my app is shutting down.<div>
<br></div><div><br><div class="gmail_quote">On Tue, Mar 20, 2012 at 10:32 AM, Simon MacMullen <span dir="ltr"><<a href="mailto:simon@rabbitmq.com">simon@rabbitmq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 20/03/12 14:23, Dave Stevens wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I frequently notice that queues which were created with autodelete are<br>
not actually deleted once there are no more consumers.<br>
</blockquote>
<br></div>
Just to be absolutely clear here: you mean they had consumers once, and then the consumers all went away? If the queue never has consumers it will not autodelete (otherwise it would autodelete as soon as you created it).<br>
<br>
If you do mean that there were once consumers and the queue is still not getting deleted, then yes, that would be wrong. We do test for this though :-) so a test program would be helpful.<br>
<br>
Cheers, Simon<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
Simon MacMullen<br>
RabbitMQ, VMware<br>
</font></span></blockquote></div><br></div>