This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: Socket's close() doesn't close connection (old bug?)
- From: Martin Egholm Nielsen <martin at egholm-nielsen dot dk>
- To: java at gcc dot gnu dot org
- Date: Tue, 08 Nov 2005 16:46:57 +0100
- Subject: Re: Socket's close() doesn't close connection (old bug?)
- References: <dkqf0k$q5g$1@sea.gmane.org>
In my eager to reproduce another bug I've stumbled across yet another
strange issue - namely that Socket's close() doesn't close underlying
socket (with no traffic), nor "wake up" a blocked read-thread (as a
consequence)...
Blah blah blah, this turned out to be reported already:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15430
Unfortunately still open ;-)
It seems that if you set the SoTimeout value, so that read() returns,
the socket will be closed after returning the blocking thread.
So I guess it's only a matter of interrupting any blocking thread when
close() is invoked - then everything will be good?!
(My naive thoughts - I'll look into the implementation in a moment to
see if this is possible in any easy matter...)
// Martin