JDK-8131045 : Obsolete JNIDetachReleasesMonitors
- Type: Enhancement
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 9
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2015-07-13
- Updated: 2017-05-17
- Resolved: 2015-10-30
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.
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.
| JDK 9 |
|---|
9 b94Fixed  |
Related Reports
|
CSR :
|
|
|
Relates :
|
Sub Tasks
|
JDK-8175237 :
|
Description
The JNIDetachReleasesMonitors flag was added to JDK 6 when it was realized that the VM was not compliant with the JNI specification regarding the release of monitors when a JNI attached thread detached - see JDK-6336479. The flag allowed for restoration of the incorrect behaviour if an application was somehow relying on it. By now all applications should themselves be JNI-spec compliant and this workaround should not be needed, so we can obsolete the JNIDetachReleasesMonitors flag in JDK 9 (accept it but take no action) and expire (remove) it in JDK 10.
Comments
|