Bunny doesn't heartbeat about bunny HOT 5 CLOSED

Heartbeats in AMQP 0.9.1 are optional. Do you want to help implementing this functionality?

from bunny.

Here is my use-case:

I have a simple worker that pulls work from a queue, acts on it and then moves onto the next item. I do this using a subscribe block. The code is neat, easy to follow and highly testable.

The problem is that when the underlying connection dies, I don't know about it until the subscribe block hits its timeout. At that point it cancels the subscription, which triggers an exception because the network connection is dead. Worst case here is a 15 min period where the worker is doing nothing.

Heartbeats seemed exactly what I wanted. Is there another way?

from bunny.

You can either implement heartbeat support or have a thread that publishes messages that won't be routed anywhere (using default exchange and a random string as routing key). At least RabbitMQ should treat connection activity as heartbeats, regardless of what the client specified as heartbeat interval.

from bunny.

Please leave this issue open. At the very least it'll answer somebody else's question on the matter. At the best, it might attract a pull request.

from bunny.

Will be solved after a rewrite

from bunny.