Enabling a client timeout

[Christian Migowski]

I've always wondered how this connect() timeout should work. As far as
I know, the behaviour for the case you are describing (packets
silently dropped by firewall) is completely steered by the TCP stack,
i.e. operating system options. In Linux you'd have to modify
"tcp_retries1", and/or "tcp_syn_retries" to get a different behaviour,
Windows sure has some similar settings somewhere in the registry.

hth,
christian!

On Sun, Jul 26, 2009 at 1:34 PM, miracle2k<michael at elsdoerfer.info> wrote:
>
> I just tried a normal Java app on Windows - the timeout there consistently
> seems to be 20 seconds, regardless of any custom settings, or the 20 secs
> default timeout in DefaultChannelConfig.
>
> I'd have to guess then that a platform specific value is ultimately in
> effect, not what is set by Netty.
> --
> View this message in context: http://n2.nabble.com/Enabling-a-client-timeout-tp3328690p3328788.html
> Sent from the Netty User Group mailing list archive at Nabble.com.
> _______________________________________________
> netty-users mailing list
> netty-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-users
>