Connection reset timeouts different on Windows vs Linux
843790Mar 25 2008 — edited Mar 25 2008I have a simple client-server application take talk via Java sockets. The server always runs on Windows while the client runs on Windows and Linux. The default socket timeout is 0 - infinite - on the client socket.
After establishing a socket connection to the server, when the client program attempts to read from the input stream (DataInputStream::read()), I physically sever the connection between the server and the client. I notice that it takes the Windows client only about 90 secs to report a "Connection reset" exception while it takes the client on Linux 15 mins for it recognize that the connection has terminated (and on Solaris it takes about 7 mins). Is this difference in timeouts "as designed" or is it a bug.
I'd appreciate your inputs.
Thanks
Ranjit