One message-queue (q-agent-notifier-port-update_fanout_91e5c8311b1b47a2b39ede94dad9a56b) be blocked ( please refer to the attached picture) Version: RabbitMQ 3.6.0 release, openstack kilo This phenomeno comes up sometimes when in the large-scale environment, when one rabbitmq message-queue be created，if no consume binded to it but the producers publish messages to queue continuously, then the queue will not be dropped forever. such conduct to the messages accumulated invalidly If I want the queue which hasn't been binded with consumers or producers to be dropped with a configurable time,how can I do? thanks CrownYoga -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160223/97776de0/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: rabbitmq_blocked_fanoutqueue.bmp Type: image/bmp Size: 3215994 bytes Desc: not available URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160223/97776de0/attachment-0001.bin>