I frequently notice that queues which were created with autodelete are not actually deleted once there are no more consumers. This is an issue because they continue to receive messages when they should instead be deleted. Am I misunderstanding the effect that the autodelete flag has on queues? Is there another explanation for this behavior?<div><br></div><div>Using rabbitmq 2.7.1 on cluster.</div><div><br></div><div>Below is json from manager web api for one such queue. Node host name removed. Note consumers&nbsp;"consumers":0 and&nbsp;"auto_delete":true</div><div><br></div><div><pre>{"memory":230544,"idle_since":"2012-3-20 10:12:51","exclusive_consumer_tag":"","messages_ready":318,"messages_unacknowledged":0,"messages":318,"consumers":0,"slave_nodes":[],"backing_queue_status":{"q1":0,"q2":0,"delta":["delta","undefined",0,"undefined"],"q3":0,"q4":318,"len":318,"pending_acks":0,"target_ram_count":"infinity","ram_msg_count":318,"ram_ack_count":0,"next_seq_id":318,"persistent_count":0,"avg_ingress_rate":0.1407138438947011,"avg_egress_rate":0.0,"avg_ack_ingress_rate":0.0,"avg_ack_egress_rate":0.0},"messages_details":{"rate":0,"interval":56241811945,"last_event":1332252771225},"messages_ready_details":{"rate":0,"interval":56241811945,"last_event":1332252771225},"messages_unacknowledged_details":{"rate":0,"interval":56241811945,"last_event":1332252771225},"consumer_details":[],"name":"bt.cs.ep.private-7c49741e-018d-48c8-aee3-e654c302176d","vhost":"/","durable":false,"auto_delete":true,"arguments":{},"node":"********"}</pre></div>