Reputation: 34145
I've got an application which has some bugs. For some reason 2 consumers are created when only one should be there - and one of them is not checked for messages anymore.
I can detect that situation by listing queues and the number of consumers on the server. Is there some way to destroy that consumer from the server side?
Upvotes: 8
Views: 29667
Reputation: 11
You need to mark you consumer as "exclusive". Then only one consumer is registered with queue and other consumers are ignored even they tries to get data from that queue.
Upvotes: 0
Reputation: 1539
consumer can be kill by rabbitmqctl
using close_connection input connectionpid
example
> rabbitmqctl close_connection "<[email protected]>" "reason here"
connectionpid can get by
> rabbitmqctl list_consumers
Listing consumers ...
send_email_1 <[email protected]> amq.ctag-oim8CCP2hsioWc-3WwS-qQ true 1 []
send_email_2 <[email protected]> amq.ctag-WxpxDglqZQN2FNShN4g7QA true 1 []
RabbitMQ 3.5.4
Upvotes: 13
Reputation: 19295
You can kill connections to the RabbitMQ broker using the rabbitmqctl
tool (see the man page) or by using the Web UI. You could also purge and delete the queue which belonged to the rogue consumer.
However, you can't kill the consumer process itself using those tools. You really should just focus on fixing the bugs in the application so that only the correct number of consumers get created.
Upvotes: 10