You have configured redelivery delay, meaning the current messages are going to be delivered while the one you just redelivered will only return to the queue in 100 ms.
So, that would be an expected behaviour... disable redelivery delay and it should work as you expected.
Aha, it makes sense now. A bit of context:
I where trying to implement a back-off strategy where I would do a rollback and rely on redeliveries if the backend system was to busy to handle the message at the moment. But I could not afford any out-of-order deliveries. I'll set redelivery-delay to 0 and roll my own exponential back-off solution at the client instead.
Thanks for the quick help,
That's an old request to implement a pause on the queue after redelivery.. which would be another feature.
Redelivery delay is really about the current message while the queue stays open.
One of the issues to decide upon the implementation is we should pause just the consumer or the whole queue? Say in cases where you have multiple consumers.