0.5.0

The past few years have seen a variety of JVM builds get adopted, from AdoptOpenJDK to OpenJ9 to upstream projects. In such a scenario, the JMA built-in, explicit whitelisting of JVMs has become a liability and a guarantee of need of ongoing maintenance.

Rather than require an explicitly modeled and white-listed JVM, this change preserves the definition of memory pools and their mapping to configuration properties, and detects
dynamically which memory pools are available in the JVM.

The information on the supported memory pools is available in DEBUG log level.

0.4.0

Add support for the following Java 11 JVMs (via @mmanciop):

• AdoptOpenJDK 11
• Oracle JDK 11
• OpenJDK 11
• SAP Machine 11

Add support for the following Java 8 JVMs (via @mmanciop):

• AdoptOpenJDK 8
• Pivotal JVM 8

Upgrade Gradle version to support Java 11 (via @mmanciop)

0.3.0

• Add support to absolute thresholds of memory utilisation. Now it is possible to have a heap dump triggered when the usage a memory pool is strictly smaller than, smaller then or equal to, exactly equal to, larger than or equal to and strictly larger to a predefined threshold. The configuration value ≶=200MB for the jma.thresholds.heap, for example, will cause heap dumps to be triggered when the size of the heap grows larger than or equal to 200MB. Supported memory sizes are B (byte), KB (kilobyte), MB (megabyte) and GB (gigabyte). The numeric value is any valid double.
• Added Gradle wrapper to repo.

0.2.0

• Make jma.command.interpreter configuration optional to better support execution of binary commands.
• Avoid log spamming when heap dumps are skipped due to frequency limitations

0.1.0

First (public) release of the Java Memory Assistant.