If the handler doesn't read the message, the consumer hangs

[arsham]

This happens when the context is cancelled and the consumer forgets to close the connection.

Options

1- There can be an intermediary channel with a that would keep the message and when the context is cancelled, it nacks.
2- Manage the connection when context is cancelled and when Consume is being called.

The second option is more robust but requires a bit of development.