[rabbitmq-discuss] Shovel messages get lost or stay unacknowledged.

[Mark Steele]

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 (
http://libkeepalive.sourceforge.net/) to force the rabbit server to do
this, but it'd be nice if it was an option that was baked in.

Mark Steele, CISSP, CSM
Bering Media Inc.


On Tue, Nov 29, 2011 at 5:55 AM, Simon MacMullen <simon at rabbitmq.com> wrote:

> On 29/11/11 08:37, Jelle Smet wrote:
>
>> I have defined a heartbeat for each configured connection Shovel
>> creates. (?heartbeat=5)
>> I haven't run into the same issue ever since, ...
>>
>
> 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.
>
> Cheers, Simon
>
> --
> Simon MacMullen
> RabbitMQ, VMware
> ______________________________**_________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.**rabbitmq.com<rabbitmq-discuss at lists.rabbitmq.com>
> https://lists.rabbitmq.com/**cgi-bin/mailman/listinfo/**rabbitmq-discuss<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/20111129/a45aae34/attachment.htm>