JDK-8341916 : Remove ProtectionDomain related hotspot code and tests
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2024-10-10
  • Updated: 2024-11-27
  • Resolved: 2024-11-18
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 24
24 b25Fixed
Related Reports
Blocks :  
JDK-8338411 - Implement JEP 486: Permanently Disable the Security Manager
Description
The following tests that depend on ProtectionDomain code in the native hotspot code will need to be removed from the ProblemList after JEP 486 is integrated. These tests depend on remaining hotspot Security Manager related code which will be removed after JEP 486 is integrated.

runtime/Dictionary/CleanProtectionDomain.java
runtime/Dictionary/ProtectionDomainCacheTest.java 0000000 generic-all
runtime/logging/ProtectionDomainVerificationTest.java 0000000 generic-all
Comments
Changeset: dfddbcaa Branch: master Author: Coleen Phillimore <coleenp@openjdk.org> Date: 2024-11-18 12:48:40 +0000 URL: https://git.openjdk.org/jdk/commit/dfddbcaab886b9baa731cd748bb7f547e1903b64
18-11-2024
A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/jdk/pull/22064 Date: 2024-11-13 11:42:11 +0000
13-11-2024
> Does protectionDomainCache disappear after this? Oh yes!
16-10-2024
Does protectionDomainCache disappear after this?
15-10-2024
Some Hotspot code that deals with ProtectionDomain should remain but there is a lot of code to cache the value of checkPackageAccess that can be removed when the security manager removal JEP is integrated. The java.lang.Class instance still has a reference to it but that's only used by the JDK code and hotspot doesn't care about it.
14-10-2024