On Thu, 17 Sep 2026 19:37:20 GMT, Kieran Farrell <[email protected]> wrote:

>> This patch adds a new jcmd diagnostic command, `VM.show_settings`, to make 
>> the existing -`XshowSettings` output available from a running VM. The 
>> command accepts the same sections as`XshowSettings` (all, vm, properties, 
>> locale, security, system, security:all, security:properties, 
>> security:providers, security:tls). 
>> 
>> HotSpot registers the new diagnostic command, validates the requested 
>> section, then calls into `sun.launcher.LauncherHelper` to reuse the existing 
>> show settings formatting and return the result as bytes for the jcmd stream. 
>> The VM settings path also passes hotspots `InitialHeapSize`, `MaxHeapSize`, 
>> and Java thread stack size into the Java helper. A new jcmd test covers VM, 
>> properties, security TLS, and invalid-input output.
>> 
>> ---------
>> - [x] I confirm that I make this contribution in accordance with the 
>> [OpenJDK Interim AI Policy](https://openjdk.org/legal/ai).
>
> Kieran Farrell has updated the pull request incrementally with one additional 
> commit since the last revision:
> 
>   make security properties current and add extra jcmd output

src/java.base/share/classes/jdk/internal/util/SecuritySettings.java line 26:

> 24:  */
> 25: 
> 26: package jdk.internal.util;

Moving this out of sun.launcher is okay but probably not jdk.internal.util as 
this is not a utility class for use in wide areas of java.base. We may end up 
creating a "new" package for this is jdk.internal.

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/31742#discussion_r4104497149

Reply via email to