RFR: 8292177: InitialSecurityProperty JFR event [v3]

Sean Coffey coffeys at openjdk.org
Tue Oct 11 11:30:28 UTC 2022

On Mon, 10 Oct 2022 20:54:58 GMT, Sean Mullan <mullan at openjdk.org> wrote:

>> modified code to have Security class hold the initial properties and provided an accessor method
> What about creating a new `JavaSecurityPropertiesAccess` class and moving the accessor method there? It seems it would be cleaner to remove the dependency on PD in the long run.

@seanjmullan  - I looked at that approach. The `SharedSecrets.getJavaSecurityAccess().getInitialProperties();` call may trigger early initialization of the `java.security.Security` class - I'm not sure if we want that. ProtectionDomain class is currently loaded early in the JDK boot cycle. 

In fact the change suggested by @AlanBateman yesterday also has possibility to trigger unnecessary loading of the Security class. I might revert to the original design where we store the cached Properties in ProtectionDomain ?


PR: https://git.openjdk.org/jdk/pull/10394

More information about the security-dev mailing list