On 26/10/12 07:28, Raviv Pavel wrote:
I find this behavior is problematic
AMQP/Rabbit could hardly do anything different - if the sole condition for auto-deletion was that there are no consumers then the queue would get deleted straight after creation, before you've had a chance to attach any consumers.
If I create an auto-delete queue (by code) and then crash before consuming, the queue will be stuck there until I delete it.
Couldn't you make the queue 'exclusive' instead of 'auto-delete'? Or, alternatively, set a lease (http://www.rabbitmq.com/ttl.html#queue-ttl). Regards, Matthias. -- You received this message because you are subscribed to the Google Groups "rabbitmq-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rabbitmq-discuss?hl=en.
