RFR: 8260349: Cannot programmatically retrieve Metaspace max set via JAVA_TOOL_OPTIONS [v2]

[David Holmes]

> 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

David Holmes has updated the pull request incrementally with one additional commit since the last revision:

  Boost max from 1MB to 9MB as 1MB was too low for Aarch64 to startup

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

Changes:
  - all: https://git.openjdk.java.net/jdk/pull/2275/files
  - new: https://git.openjdk.java.net/jdk/pull/2275/files/cf887704..8c814dce

Webrevs:
 - full: https://webrevs.openjdk.java.net/?repo=jdk&pr=2275&range=01
 - incr: https://webrevs.openjdk.java.net/?repo=jdk&pr=2275&range=00-01

  Stats: 1 line in 1 file changed: 0 ins; 0 del; 1 mod
  Patch: https://git.openjdk.java.net/jdk/pull/2275.diff
  Fetch: git fetch https://git.openjdk.java.net/jdk pull/2275/head:pull/2275

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