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

Matthias Radestock matthias at rabbitmq.com
Tue Nov 29 15:17:06 GMT 2011


On 29/11/11 14:40, Mark Steele wrote:
> 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.

You can control Rabbit's tcp options through the Erlang kernel app's 
inet_default_connect_options and inet_default_listen_options. See 

However, iirc some firewalls suppress keepalive. AMQP's heartbeats 
provide a more reliable mechanisms.



More information about the rabbitmq-discuss mailing list