Re: Strange Socket problem?
Tom Hawtin wrote:
Knute Johnson wrote:
Since upgrading to 1.6 I have seen on occasion a socket disconnect
that isn't detected by the client end. No exception is thrown and the
stream I/O stays blocked. The host end definitely shows the
connection closed. I can't reproduce it which is going to be a
problem if I want to file a bug report. Has anybody else seen this
since upgrading to 1.6?
Are you sure it's not just coincidental that the occasional connection
drops after you upgraded to 1.6? If there's a network problem it often
wont show until sometime after a write from that socket, but that's
nothing to do with Java.
Tom Hawtin
I've got some software in the field that is now occasionally hanging
when it didn't before. Although that problem is newer than the change
to 1.6. I'm working on another program and the client in that pair has
hung a few times on me while the host has definitely shown a disconnect.
And it is very possible that it is all coincidental. The client end
that has missed the disconnect in both cases has only been reading.
Reads have always been a reliable way to detect disconnects in the past.
I have put a timer into the software in the field to check to make sure
that the read thread has terminated. We had an actual failure this
morning and it was not corrected because the read thread did not
terminate even when the socket was closed. No exception was thrown.
This program is very complicated though and it is quite possible that my
fix was not correct. I've got a new fix going in tonight (why is it
that it always has to be late at night :-).
Oh and one more tidbit is that on the new project I'm working on the
hang occurred with the host and client on the same machine.
All the computers are running Windows XP which just adds to the
entertainment value.
Thanks very much for your interest.
--
Knute Johnson
email s/nospam/knute/