[rabbitmq-discuss] How to keep-alive a purely receiving connection?

Matthias Radestock matthias at rabbitmq.com
Sat Jul 20 00:07:34 BST 2013


On 19/07/13 22:00, Kapil Goyal wrote:
> We are using two connections, one for sending data and one for
> receiving. We also want to utilize heartbeat functionality to keep the
> connections alive.

You do realise that most client libraries will do that for you, right?

> I understand that client must send some data (within heartbeat interval)
> to RabbitMQ even on the receiving connection to keep it alive.


> Question is, if RabbitMQ starts blocking publishing connections during
> flow-control, would it also block this receiving connection on a
> heartbeat-publish?

No. Heartbeats are not publishes. A publishing connection is one over 
which content-bearing AMQP methods are received, of which there is just 
one defined in the spec, namely basic.publish.


More information about the rabbitmq-discuss mailing list