JDK-4470470 : (ch) Asynchronous closing and interruption broken (win, sol)
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.nio
  • Affected Version: 1.4.0
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_2000
  • CPU: x86
  • Submitted: 2001-06-15
  • Updated: 2009-04-08
  • Resolved: 2002-06-07
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
1.4.1 hopperFixed
Related Reports
Duplicate :  
JDK-4648468 - (ch) Asynchronous closing and interruption generally broken
Duplicate :  
JDK-4647447 - (so) ServerSocketChannel does not interrupt (win, sol)
Relates :  
JDK-4504001 - Check NIO native code to ensure that it restarts any sys calls
Description
The functionality specified in the AbstractInterruptibleChannel interface
does not always work on Solaris and Windows.  In particular, if one thread
attempts to close a channel upon which another thread is currently blocked,
the first thread stalls until the second thread's I/O operation is complete.
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: hopper FIXED IN: hopper INTEGRATED IN: hopper VERIFIED IN: hopper
14-06-2004
EVALUATION On windows, this test fails because a channel blocked in read stays blocked when the file descriptor is closed. On other platforms closing the fd kicks a thread out of a blocked read on that fd. ###@###.### 2001-10-25 Another problem is a deadlock where a thread is blocked in reading and holds the read lock, then another thread tries to shutdown the socket but cannot because it needs the read lock to do so and the test hangs. ###@###.### 2001-10-26
26-10-2001