[rabbitmq-discuss] AMQP heartbeat - Expected behaviors
matthias at rabbitmq.com
Tue Jul 3 20:27:30 BST 2012
On 03/07/12 20:17, Matt Pietrek wrote:
> We've recently started using the heartbeat connection option, and I need
> to understand them precisely. I understand that both client and server
> side can send heartbeat frames, that other activity can substitute for a
> heartbeat frame, and that the intervals are negotiated during tuning.
> What's confusing me is this: Some threads such at this one imply that
> the server "periodically sends heartbeat frames to the client and waits
> for its response."
That's nonsense. Ignore. There is no response.
> Confounding matters, at least three client libraries I've looked at
> (including Pika and .NET) explicitly check for heartbeat frame (i.e., 8)
> and then do nothing with them.
I don't know enough about pika, but the .net client calls
NotifyHeartbeatThread(); on each iteration of the frame reading loop.
It's ok not to do anything special with heartbeat frames; what matters
is that *a* frame arrives in time.
More information about the rabbitmq-discuss