RFR: JDK-8327769: jcmd GC.heap_dump without options should write to location given by -XX:HeapDumpPath, if set [v10]
Matthias Baesken
mbaesken at openjdk.org
Fri Apr 5 11:04:14 UTC 2024
On Fri, 5 Apr 2024 08:57:09 GMT, Sandra Payne <duke at openjdk.org> wrote:
> Many customers may see such a change as a regression, as they rely on separation of location for heap dumps generated by the > JVM at OOME and heap dumps manually pulled by various other processes attaching to the JVM.
With this change it is still possible to have separation (nobody stops users from using jcmd with the filename option, this is still available).
Or do you think that some tool/script developers would maybe (with this change) in future more use the -XX:HeapDumpPath for **_both_** OOME and jcmd, so that customers would run into this scenario ?
-------------
PR Comment: https://git.openjdk.org/jdk/pull/18190#issuecomment-2039511382
More information about the serviceability-dev
mailing list