[rabbitmq-discuss] heartbeat bug

Emile Joubert emile at rabbitmq.com
Tue Mar 27 10:47:18 BST 2012

Hi Aaron,

On 26/03/12 21:01, Aaron Westendorf wrote:
> required to do so. At this time, haigha only responds to heartbeats
> and does not initiate a client-side loop. As far as I know and have
> observed in other implementations, this is standard practice. In other
> words, I think both client and server are operating within spec.

If a client requests heartbeats then it must be able to send heartbeats
actively (after connection.tune). Depending on the traffic patterns, a
client that only echoes server heartbeats will not satisfy the
requirements of the spec. If traffic becomes one-way (e.g. asynchronous
calls from the server to the client like basic.deliver) then an echoing
client will not send enough heartbeats and the server will drop the
connection. It looks like that is what your trace shows.

If a client does not implement heartbeating then it must request no
heartbeats during connection tuning, and not send any heartbeats. If you
are aware of other RabbitMQ clients with the same problem then please
let us know so that the authors can be alerted.


More information about the rabbitmq-discuss mailing list