We've seen similar issues with long lived connections being killed by firewalls. I'd recommend Rabbit add TCP_KEEPALIVE to the socket options. We've worked around it by using libkeepalive (<a href="http://libkeepalive.sourceforge.net/">http://libkeepalive.sourceforge.net/</a>) to force the rabbit server to do this, but it'd be nice if it was an option that was baked in.<div>
<br clear="all">Mark Steele, CISSP, CSM<br>Bering Media Inc.<br><div><br></div><br><div class="gmail_quote">On Tue, Nov 29, 2011 at 5:55 AM, Simon MacMullen <span dir="ltr"><<a href="mailto:simon@rabbitmq.com">simon@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 class="im">On 29/11/11 08:37, Jelle Smet wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I have defined a heartbeat for each configured connection Shovel<br>
creates. (?heartbeat=5)<br>
I haven't run into the same issue ever since, ...<br>
</blockquote>
<br></div>
Well, that's good news at least. It's possible some networking thing somewhere in between might be failing to route packets for TCP connections that have been idle for a while. We've seen intimations of such things before I think.<br>
<br>
Cheers, Simon<br><font color="#888888">
<br>
-- <br>
Simon MacMullen<br>
RabbitMQ, VMware<br>
______________________________<u></u>_________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.<u></u>rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/<u></u>cgi-bin/mailman/listinfo/<u></u>rabbitmq-discuss</a><br>
</font></blockquote></div><br></div>