On Wed, 18 Feb 2026 17:55:54 GMT, Kieran Farrell <[email protected]> wrote:
>> The goal of this PR is to add a means of exposing security properties at >> runtime to aid the debugging security related issues/misconfigurations etc. >> Currently, only initial security properties set at start up can be exposed >> via the `InitialSecurityProperty` JFR event. >> >> This patch introduces a new jcmd diagnostic command `VM.properties`, which >> enables developers to print either the current system properties or security >> properties of a running Java process via command-line arguments (-system or >> -security). To avoid clutter within the jcmd command list, the old >> `VM.system_properties` command is hidden, but not removed so will not break >> existing usages. The implementation of each is shared to reduce duplication. > > Kieran Farrell has updated the pull request incrementally with one additional > commit since the last revision: > > newline test/hotspot/jtreg/serviceability/dcmd/vm/SecurityPropertiesTest.java line 40: > 38: * java.management > 39: * jdk.internal.jvmstat/sun.jvmstat.monitor > 40: * @run testng SecurityPropertiesTest Probably best to have this test start out as a JUnit rather than TestNG tests as there is effort to try to have new tests not use TestNG. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/29124#discussion_r2823878639
