On Fri, 10 Jul 2026 08:12:36 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: > > revert mistaken change src/java.base/share/classes/sun/launcher/LauncherHelper.java line 193: > 191: } > 192: > 193: public static byte[] showSettingsBytes(String optionFlag, @kieran-farrell Have you looked into moving the showSettings code to jdk.internal to be with the other supporting methods? That would allow it be used by the java launcher and the upcall from the VM. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/31742#discussion_r3612913533
