JDK-8202331 : Obsolete support for commercial features
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 11
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2018-04-26
  • Updated: 2019-06-20
  • Resolved: 2018-06-22
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 11 JDK 12
11 b20Fixed 12Fixed
Related Reports
Blocks :  
Sub Tasks
JDK-8205536 :  
Description
Once JFR has been integrated the support for commercial features should be removed.
Comments
Please also include updating or removing the following test: serviceability/commercialfeatures/TestCommercialFiles.java The reference to jfr was removed, but this test still exists and still checks for missioncontrol in commercial builds.
19-05-2018

Changed description to "Obsolete".
01-05-2018

See JDK-8199367, which is for open sourcing "serviceability" tests. A number of closed serviceability tests related to UnlockCommercialFeatures pop up there, including: serviceability/commercialfeatures/TestJcmdHelpCommercialFeatures.java serviceability/commercialfeatures/TestJcmdUnlockCommercialFeatures.java serviceability/commercialfeatures/TestUnlockCommercialFeaturesFlag.java Will this CR handle removing the Jcmd support, and also the above tests at the same time? There are other serviceability/commercialfeatures tests mentioned in JDK-8199367, but they are all either already in the JFR webrev for JDK-8199712, or I requested that they be added.
30-04-2018

Do we intend to deprecate or obsolete? Given there are no commercial features left to unlock the flag would be a no-op either way for all practical intents and purposes. The only visible difference is whether the error message says "deprecated" or "obsolete". Either way seems fine. Deprecate for 11, obsolete in 12, expire in 13. Gives time for customers to update scripts etc.
30-04-2018