JDK-8230940 : Obsolete MonitorBound
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 15
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2019-09-13
  • Updated: 2020-05-11
  • Resolved: 2020-05-03
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.
JDK 15
15 b22Fixed
Related Reports
Relates :  
JDK-8230941 - Remove MonitorBound
Relates :  
JDK-8230938 - Deprecate MonitorBound
Description
MonitorBound was deprecated in JDK 14 under JDK-8230938, and now needs to be obsoleted.
Comments
URL: https://hg.openjdk.java.net/jdk/jdk/rev/4198213fc371 User: dcubed Date: 2020-05-03 14:04:47 +0000
03-05-2020
> Obsoletion checklist: > - delete all code relating to the options Done. > - update any test that may be specifying the options (e.g. VMDeprecatedOptions test) Did not find any tests in the repo that uses the MonitorBound option, but I do have some in my personal ObjectMonitor stress kit. > - move the flags to the "obsoleted" section of the special flags table Done. > - update any documentation that may refer to these flags Google only found JDK-* bugs that referred to MonitorBound. No man pages were found.
01-05-2020
As per my comments above: > We just hit build 20 of JDK 15 and the special flag validation test is now failing because this flag has not yet been obsoleted. > I'm bumping the validation build to 25 to give a little more time for this to be fixed. that test is in tier1.
27-04-2020
How come this RFE has the tier1 label? Are there test failures in tier1 due to something that will be fixed here?
27-04-2020
I'm bumping the validation build to 25 to give a little more time for this to be fixed.
16-04-2020
We just hit build 20 of JDK 15 and the special flag validation test is now failing because this flag has not yet been obsoleted.
16-04-2020
Obsoletion checklist: - delete all code relating to the options - update any test that may be specifying the options (e.g. VMDeprecatedOptions test) - move the flags to the "obsoleted" section of the special flags table - update any documentation that may refer to these flags
18-12-2019