You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Zoran Regvart <zo...@regvart.com> on 2021/07/13 08:55:13 UTC
Re: TCP - Netty: reconnect after connection becomes idle
Hi Aaron,
in situations like this it is better to have the keep alive enabled.
In fact it is the mechanism by which you can detect that a TCP
connection has been left half open. Have a look here:
https://tldp.org/HOWTO/TCP-Keepalive-HOWTO/overview.html
In my experience a better option would be to look into setting a
shorter keep alive interval, and that is OS dependent in most cases.
I'd also investigate network equipment on your end to see if keep
alive packets are getting dropped by a switch or a firewall on your
end.
zoran
On Tue, Jul 13, 2021 at 10:47 AM Aaron Van Stappen
<aa...@aviobook.aero> wrote:
>
> Hi Camel experts,
>
> We are connecting to one of our providers via a TCP connection with a Netty component in Camel. Because of some (strange) issue on out provider's side, the connection can become idle and we have to reconnect. They suggest a reconnection after a timespan of 30 seconds. We were looking at setting the "keepAlive" option to false. However, we cannot find if we can configure the time after which it is considered inactive.
> Do you guys know where we might find the answers to handle this? This would be much appreciated.
>
> Kind regards,
> Aaron Van Stappen
--
Zoran Regvart