medium10 pts · first answer countsmessage-queuesreliability

One bad message blocks the queue

One malformed message makes your consumer throw. It is redelivered again and again, and newer messages pile up behind it. What is the standard fix?

A.Delete and recreate the queueB.Add more consumer instances so other workers keep processing new messages while one retries the bad oneC.Turn off acknowledgements so messages are not redeliveredD.After a few failed attempts, move it to a dead-letter queue and alert on it

← Docker rebuild reinstalls everything Worker crash with auto-ack →