to use. Among Sun's Java implementations, only the Solaris version has
implemented the throwing of this exception when a thread blocked in an I/O
operation is interrupted via the Thread.interrupt() method. It is very
difficult, if not impossible, to implement this functionality on Win32 (see,
e.g., 4154947) and on some other Unix variants. InterruptedIOException should
therefore not be a required part of the J2SE platform specification, and the
relevant Javadoc should be updated to reflect this.
- relates to
-
JDK-4764778 Interrupted thread can't load classes from classes directory (sol)
- Closed
-
JDK-4989068 PrintStream.println() prints nothing in interrupted thread (sol)
- Closed
-
JDK-6375934 (cl) thread interruption interferes with classloading (sol)
- Closed
-
JDK-6450036 PrintStream.flush() clears thread interrupt flag (sol)
- Closed
-
JDK-6554406 Change switch UseVMInterruptibleIO default to false (sol)
- Closed
-
JDK-4154947 JDK 1.1.6, 1.2/Windows NT: Interrupting a thread blocked does not unblock IO
- Closed
-
JDK-4250457 InputStream.read() contains undocumented behaviour when interrupted
- Closed
-
JDK-6296152 System.err cannot print ThreadDeath
- Closed
-
JDK-6348631 remove the use of the HPI library from Hotspot
- Closed
-
JDK-6491364 Document Solaris-specific Hotspot switch UseVMInterruptibleIO as a Solaris platform rel note item
- Resolved
-
JDK-6382902 VM interrupted I/O feature put on an option switch (sol)
- Closed
-
JDK-8338716 Re-visit "interrupt handling" in jdk.internal.loader.Resource
- Resolved
-
JDK-7188233 UseVMInterruptibleIO flag deprecate for JDK8
- Closed
-
JDK-4329256 interrupted thread no longer produces output (sol)
- Closed
-
JDK-4514257 Thread.interrupt() on InputStream.read() fails
- Closed
-
JDK-4992463 ClassLoading fails if the Thread's interrupt status is set
- Closed