Consumer puts the message in noack as soon as the message is received

12 views
Skip to first unread message

MS

unread,
Jun 13, 2020, 6:39:33 PM6/13/20
to rabbitmq-discuss
I am using AMQP 1.0 for RabbitMQ.
For all the other pub/sub between various containers, it is working as expected.
But when the message is published to a queue, which the consumer receives the message and then perform a compute heavy task, as soon as the message is sent to this queue, it automatically gets into noack list even when the message was actually consumed and the callback function started performing its tasks. After some time the message becomes ready and is again consumed (duplicate and re-runs the pipeline) and then again becomes noack.
So for 1 message published, the consumer keeps moving it from noack to ready to noack and so on and keeps consuming the message and re-running the task infinitely.

MS

unread,
Jun 13, 2020, 7:04:16 PM6/13/20
to rabbitmq-discuss
Also, using the rabbitmqadmin is it possible to permanently set the ack_required to False for all the consumers subscribed to a queue?
Reply all
Reply to author
Forward
0 new messages