Re: Hang on socket close after connection reset or connection timed
out
Esmond Pitt wrote:
Knute Johnson wrote:
You want to see the code, there isn't a write in it?
Sure, if you like. Send it to me privately via
http://www.telekinesis.com.au/wipv3_6/people.A21. There are other
explanations for ECONNRESET but they usually emanate from the other end
and they don't have anything to do with read blocks. Does the writing
end fiddle with SO_LINGER? or is it MS IIS by any chance (which does)?
There's also the local condition 'software caused connection abort',
WSAECONNABORTED (10053), but that's not what's happenin here. For more
info on that see
http://forum.java.sun.com/thread.jspa?forumID=11&threadID=748677.
Here is a really simple example. Run s then c. If you don't get a
java.net.SocketExcepion: Connection reset I'll eat my hat (or a
reasonable facsimile like a cheeseburger). I'm not being rude but I
won't be able to reply for a week to 10 days. Sorry.
import java.io.*;
import java.net.*;
public class s {
public static void main(String[] args) throws Exception {
ServerSocket ss = new ServerSocket(1111);
Socket s = ss.accept();
Thread.sleep(1000);
}
}
import java.io.*;
import java.net.*;
public class c {
public static void main(String[] args) {
try {
Socket s = new Socket("127.0.0.1",1111);
System.out.println(
"connected to: " + s.getInetAddress().getHostAddress());
InputStream is = s.getInputStream();
is.read();
} catch (Exception e) {
System.out.println(e);
}
}
}
--
Knute Johnson
email s/nospam/knute/