Integrated: 8260349: Cannot programmatically retrieve Metaspace max set via JAVA_TOOL_OPTIONS

[David Holmes]

On Thu, 28 Jan 2021 02:40:08 GMT, David Holmes <dholmes at openjdk.org> wrote:

> A simple but long standing bug whereby the MemoryPool MXBean only sees the value of MaxMetaspaceSize if it was set directly on the command-line and not by other means (e.g. env var).
> 
> Fix is to check !FLAG_IS_DEFAULT rather than FLAG_IS_CMDLINE.
> 
> Expanded regression test added (based on the reproducer in the JBS issue) that checks all the ways to set the flag: cmd-line, env-var, hotspotrc file
> 
> Testing: regression test (before and after fix)
>              tiers 1-3 (in progress)
> 
> Thanks,
> David

This pull request has now been integrated.

Changeset: b6a73673
Author:    David Holmes <dholmes at openjdk.org>
URL:       https://git.openjdk.java.net/jdk/commit/b6a73673
Stats:     123 lines in 2 files changed: 120 ins; 0 del; 3 mod

8260349: Cannot programmatically retrieve Metaspace max set via JAVA_TOOL_OPTIONS

Reviewed-by: shade, stuefe

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

PR: https://git.openjdk.java.net/jdk/pull/2275