this bug seems to be a race condition that queue.declare is handled before mq delete the.queue.
and the client continous basic.consume on an non-exist queue is definitely raise an.error.
This bug has been fixed in 1.5.1 by using kombu implemented ensure.
Maybe you should use cli like this, rabbitmqctl list_queues |grep replyxxx
this bug seems to be a race condition that queue.declare is handled before mq delete the.queue.
and the client continous basic.consume on an non-exist queue is definitely raise an.error.
This bug has been fixed in 1.5.1 by using kombu implemented ensure.
Maybe you should use cli like this, rabbitmqctl list_queues |grep replyxxx