It's probably your firewall.�Many firewalls have built-in idle timers. Your clients are likely in a consuming loop where there are no messages, and hence the idle timer kicks in and kills your connections.<div><br></div>
<div>Some options:</div><div><ul><li>You can try getting your Rabbit server and clients to utilize TCP keepalives</li><li>Setup libkeepalive on your server</li><li>Use AMQP heartbeats (probably the best option) to keep packets flowing.</li>
</ul><div><div><br clear="all">Mark Steele, CISSP, CSM, GPEN<br>Bering Media Inc.<br><div><br></div>
<br><br><div class="gmail_quote">On Tue, Jul 3, 2012 at 9:50 AM, Deelo55 <span dir="ltr"><<a href="mailto:dwayne.dsouza@gmail.com" target="_blank">dwayne.dsouza@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I'll need to allocate some time to this...I'm not very familiar with network<br>
traffic analysis.<br>
<br>
--<br>
View this message in context: <a href="http://rabbitmq.1065348.n5.nabble.com/RabbitMQ-subscriber-loses-connection-across-firewalls-after-long-idle-tp20480p20558.html" target="_blank">http://rabbitmq.1065348.n5.nabble.com/RabbitMQ-subscriber-loses-connection-across-firewalls-after-long-idle-tp20480p20558.html</a><br>
Sent from the RabbitMQ mailing list archive at Nabble.com.<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></div></div></div>