Can I set an explicit task timeout for RabbitMQ consumer?
<p>I understand that RabbitMQ with ack, by default, will re-queue the message if it detects that the consumer/worker has died.</p>

<p>What about the situation where the consumer/worker is still alive but its process has stalled out for too long and didn't ack?</p>

<p>I would like to set an explicit time that says that if a message has been dispatched to a consumer but that consumer has held the message without ack for too long that the message gets re-queued.</p>

<p>I recognize that this might result in messages getting processed in duplicate but sometimes the consequence of that is not as bad as delayed message delivery.
It can also happen with errant exception handling if something get swallowed, the task terminates, and the message is never ack'd and never re-queued.</p>