[rabbitmq-discuss] RabbitMQ subscriber loses connection across firewalls after long idle

[Mark Steele]

Oh, and you can also re-configure your firewall to stop that idle timer.

Mark Steele, CISSP, CSM, GPEN
Bering Media Inc.

On Tue, Jul 3, 2012 at 10:04 AM, Mark Steele <msteele at beringmedia.com>wrote:

> 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.
>
> Some options:
>
>    - You can try getting your Rabbit server and clients to utilize TCP
>    keepalives
>    - Setup libkeepalive on your server
>    - Use AMQP heartbeats (probably the best option) to keep packets
>    flowing.
>
>
> Mark Steele, CISSP, CSM, GPEN
> Bering Media Inc.
>
>
>
>
> On Tue, Jul 3, 2012 at 9:50 AM, Deelo55 <dwayne.dsouza at gmail.com> wrote:
>
>> I'll need to allocate some time to this...I'm not very familiar with
>> network
>> traffic analysis.
>>
>> --
>> View this message in context:
>> http://rabbitmq.1065348.n5.nabble.com/RabbitMQ-subscriber-loses-connection-across-firewalls-after-long-idle-tp20480p20558.html
>> Sent from the RabbitMQ mailing list archive at Nabble.com.
>> _______________________________________________
>> 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/20120703/d832dc79/attachment.htm>