<font face="trebuchet ms,sans-serif">This is something I was unaware of, although I knew heartbeats were in place. Does that mean that whatever client library I'm using, if for any reason the client does not respond to two consecutive server heartbeats then the server will close the connection and the client has to create a new one to set-up the communication once again?<br>
</font><br><div class="gmail_quote">On Fri, Jul 8, 2011 at 00:21, Matthew Sackman <span dir="ltr"><<a href="mailto:matthew@rabbitmq.com">matthew@rabbitmq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">On Thu, Jul 07, 2011 at 10:22:09AM -0700, Dorian Raymer wrote:<br>
> Is it possible to configure the broker such that it tolerates missing N<br>
> heartbeats from the client before timing out? (It currently times out after<br>
> 2*heartbeat_period, if I'm not mistaken.)<br>
<br>
</div></div>You are not mistaken, and no, there is no way of altering that without a<br>
recompile.<br>
<br>
Matthew<br>
_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
</blockquote></div><br>