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: RFC: Too many race conditions.


Florian Weimer wrote:
* David Daney:

I have been thinking about:

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29604

My inclination is to do nothing.  My analysis (int the bug report),
makes me think that to fix the race, all I/O operations would have to
enter  a  synchronized block twice.  This would create a tremendous
overhead.

Opinions?

| Any thread currently blocked in an I/O operation upon this socket | will throw a SocketException.

<http://java.sun.com/j2se/1.4.2/docs/api/java/net/Socket.html#close()>

This requires a fairly elaborate wrapper anyway. 8-(
For the most part I think we handle the asynchronous close on a Socket correctly. It is the race in all I/O code when close is called from a different thread than other I/O operations that concerns me.

David Daney


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