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?)

From: Florian Weimer <fw at deneb dot enyo dot de>
To: Martin Egholm Nielsen <martin at egholm-nielsen dot dk>
Cc: java at gcc dot gnu dot org
Date: Wed, 09 Nov 2005 13:59:10 +0100
Subject: Re: Socket's close() doesn't close connection (old bug?)
References: <dkqf0k$q5g$1@sea.gmane.org> <dkqh9i$3fr$1@sea.gmane.org><m31x1rezww.fsf@localhost.localdomain><878xvycnsz.fsf@mid.deneb.enyo.de> <dksddn$kpt$1@sea.gmane.org>

* Martin Egholm Nielsen:

>> 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?

There is no solution because the desired behavior is not consistent.

I'm not familiar with the Java behavior, but it's likely that you
explicitly need to wake up threads which are waiting in some operation
on the socket.

References:
- Re: Socket's close() doesn't close connection (old bug?)
  - From: Martin Egholm Nielsen
- Re: Socket's close() doesn't close connection (old bug?)
  - From: Martin Egholm Nielsen
- Re: Socket's close() doesn't close connection (old bug?)
  - From: Tom Tromey
- Re: Socket's close() doesn't close connection (old bug?)
  - From: Florian Weimer
- Re: Socket's close() doesn't close connection (old bug?)
  - From: Martin Egholm Nielsen

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