<HTML><HEAD><META content="text/html; charset=UTF-8" http-equiv="Content-Type"></HEAD><BODY>As far as I know, SO_TIMEOUT does not affect the success rate of packet deliveries. It just tells how soon socket read() should return before it receives data so that the application can do something else till the next read() attempt.<BR>
<BR>
Netty uses SO_TIMEOUT internally to check if there is any pending setInterestOps() request every second.<BR>
<BR>
HTH<BR>
<BR>
chudak wrote:<BR>
> There doesn't appear to be any way to do this. We can set the connect timeout<BR>
> by using the options method of the client bootstrap, e.g.:<BR>
><BR>
> bootstrap.setOption("connectTimeoutMillis", 30);<BR>
><BR>
> We can also set other socket options, e.g.:<BR>
><BR>
> bootstrap.setOption("tcpNoDelay", true);<BR>
><BR>
> We are running our netty client on a mobile device and in low network<BR>
> coverage situations where we are getting lots of packet loss, especially<BR>
> during the SSL handshake, the connection hangs indefinitely.<BR>
><BR>
> Any reason this isn't supported, especially for OIO?<BR>
><BR>
><BR>
><BR>
> --<BR>
> View this message in context: http://netty-forums-and-mailing-lists.685743.n2.nabble.com/Setting-SO-TIMEOUT-on-client-socket-channel-tp6938557p6938557.html<BR>
> Sent from the Netty User Group mailing list archive at Nabble.com.<BR>
> _______________________________________________<BR>
> netty-users mailing list<BR>
> netty-users@lists.jboss.org<BR>
> https://lists.jboss.org/mailman/listinfo/netty-users</BODY></HTML>