Channel.reject not working immediately about bunny HOT 1 CLOSED

Please post your questions to the mailing list.

A traffic capture would be able to confirm but your code seems to be blocking the consumer dispatch loop. 60 seconds is the default peer unavailability detection timeout. Consumer deliveries are dispatched to a thread pool which only has a single thread (to eliminate any unexpected concurrency hazards) by default.
That's my best guess anyway, server logs, Bunny debug logs and a traffic capture will eliminate any need to guess what is going on.

A much better approach with long-running actions would be to hand over this task to a thread pool of your own, or maybe even a one-off thread if the rate isn't going to be high. A block passed to it should capture the channel reference since you can only acknowledge or re-queue on the same channel the delivery was on. You also have to keep in mind that the channel may be closed by then. This means the delivered message was automatically requeued and will be delivered, to this consumer or another instance.

from bunny.