JDK-6375934 : (cl) thread interruption interferes with classloading (sol)
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.lang:class_loading
  • Affected Version: 6
  • Priority: P3
  • Status: Closed
  • Resolution: Not an Issue
  • OS: solaris
  • CPU: generic
  • Submitted: 2006-01-23
  • Updated: 2024-04-12
  • Resolved: 2013-09-08
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
tbdResolved
Related Reports
Relates :  
Relates :  
Relates :  
Description
The review of the suggested fix for CR 4764778 makes it clear that additional fixes are probably required to prevent thread interruption from interfering with class loading on Solaris. See the comments for additional details.

Comments
The issues in this bug are historical now. The UseVMInterruptibleIO option was introduced in JDK 6 to allow Solaris customers disable interruptible I/O if they needed to, in JDK 7 then it was disabled by default. This means that the issues in this bug report should not long be a concern.
08-09-2013

With the deprecation and impending removal of interruptible I/O is this still an issue that needs attention?
07-10-2012

EVALUATION The input needed to figure this out hasn't been forthcoming and the status wasn't updated earlier to reflect the lack of complete understanding in this area (i.e. it seemed clear cut and got more involved the further the investigation was pushed). This fix is (or perhaps these fixes are) at risk of not happening for Mustang.
08-06-2006

EVALUATION This really needs to get into Mustang. There is little doubt that programs may file with interrupted classloading via network paths and there is a hypothetical risk of corrupted class files (hypothetical, but with growing proof just waiting for a test case to be demonstrated).
24-01-2006