[rabbitmq-discuss] Heartbeat vs timeout in .NET code

Arun Rao arunrao.seattle at gmail.com
Fri Apr 11 09:47:43 BST 2014

Actually, I know that already - Client sends a 62 byte packet (of Type:
Heartbeat) to server and server responds with a zero (payload) length
packet as the response.

My specific question was - When does .NET RabbitMQ client that negotiates
only Heartbeat argument with the RabbitMQ server timeout? Is that again 2
skipped heartbeats as you mentioned above? If so, Timeout value in
Management UI for .NET clients should be twice the value?


On Fri, Apr 11, 2014 at 1:34 AM, Michael Klishin <mklishin at gopivotal.com>wrote:

> On 11 April 2014 at 11:51:27, Arun Rao (arunrao.seattle at gmail.com) wrote:
> > > So, is that timeout value just for UI or is that also when RabbitMQ
> > connection times out due to inactivity (in which case timeout
> > precedes heartbeat)?
> It is a interval at which client and server exchange heartbeat frames.
> 2 skipped heartbeats mean the peer should be considered unreachable.
> --
> MK
> Software Engineer, Pivotal/RabbitMQ
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140411/054ebd08/attachment.html>

More information about the rabbitmq-discuss mailing list