This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Socket's close() doesn't close connection (old bug?)


Hi Florian,

Martin> So I guess it's only a matter of interrupting any blocking thread when
Martin> close() is invoked - then everything will be good?!

I've always thought this bug to be rather strange, as I would have
expected the kernel to notify all read()ers on an fd that was closed
out from under them.  Most likely this just points out some flaw in my
understanding though.

This has been discussed on linux-kernel, see <http://marc.theaimsgroup.com/?t=99183809500003>.
Call me stupid, but I didn't see anybody agreeing on a solution, right?

It seems that one should never block forever, if not satisfied with the possibility to get stuck forever... :-)

BR,
 Martin


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]