Replies: 3 comments 5 replies
-
Which version of RabbitMQ are you using for testing this? |
Beta Was this translation helpful? Give feedback.
1 reply
-
Ok it seems like if you use basic.reject it works as described but if you use basic.nack it doesn't. |
Beta Was this translation helpful? Give feedback.
4 replies
-
This turned out to be a quirk of the managment UI which has been addressed in rabbitmq/rabbitmq-server#9715 When using a client library it always works as documented. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the bug
I am trying to implement a system where consumers processes as many messages as possible from a queue, skipping any unprocessable ones, but leaving them in the queue for later. I was hoping to implement this using Quorum Queues, as the documentation states that:
Based on this, I switched my queues from classic to quorum and expected to see the consumer process each message, skipping (requeuing) any unprocessable ones, and ending up "rotating" through the failed ones. Instead, I am observing that the first unprocessable message blocks the queue, and is continuously processed over and over by the consumer. According to this thread on the mailing list:
This seems to imply that quorum queues can not solve my use case. Is the documentation misleading?
Reproduction steps
Expected behavior
I expect to retrieve message B.
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions