Ok, Jean-Francois, this is not a Grizzly Issue. It is application
independent:
When a packet could not be transmitted, it is retransmitted x times, after
that the socket is disconnected by the underlying operating system.
On debian (linux in general?) the default retransmission count is 15.
The value can be adjusted here: /proc/sys/net/ipv4/tcp_retries2. Time
between retransmissions grows exponentially! Setting it to 8 for example
disconnects the socket after about 3min.
On Windows OS' the count can be adjusted here (did not try it out):
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters
TcpMaxDataRetransmissions
Bye
Markus
--
View this message in context: http://www.nabble.com/Comet-Streaming-Timeout-tp24429583p24773423.html
Sent from the Grizzly - Users mailing list archive at Nabble.com.