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.