Clarify behavior for Delivery Acknowledgment Timeout

[ronan-f]

From reading this documentation I can see that there is a timeout mechanism for unacked messages. What isn't clear to me from reading it is whether or not those messages will be requeued or is the expectation that the application will configure a dead letter queue to handle this?

My workflow is:

1. Producer sends a message
2. A consumer receives the message but does not ack it
3. The timeout threshold is reached

Will this message be requeued?

[michaelklishin]

I will convert this issue to a GitHub discussion. Currently GitHub will automatically close and lock the issue even though your question will be transferred and responded to elsewhere. This is to let you know that we do not intend to ignore this but this is how the current GitHub conversion mechanism makes it seem for the users :(

[michaelklishin]

It will be requeued since the timeout simply causes the channel to be closed.

[michaelklishin]

An potentially important addition to the above: only deliveries for consumers that use manual acknowledgements will be requeued.
You cannot realistically hit the delivery timeout with automatic acknowledgements but a single channel can be used by multiple
consumers in different modes, at least in theory.

[ronan-f]

That's great @michaelklishin. Thanks a million for a prompt response. Happy to open a PR to clarify that in the docs if it would be helpful.

Edit: Looks like the change has already been committed! 🚀