3.0.3

What's Changed

• fix heap dumps on instances except 0 by @dheidemann in #31

New Contributors

• @dheidemann made their first contribution in #31

Full Changelog: 3.0.2...3.0.3

3.0.2

Rebuilt for compatibility with newer Microsoft Windows version

3.0.1

Fix version number in plugin metadata

3.0.0

New Features:

• Setting the local output of the heap dump via --local-dir
• Setting the target of the heap dump in the container via --container-dir
• If a file system service is bound to the application container heap dumps are now automatically dumped to a path on this file system service instead
• The CLI now checks whether ssh is enabled and throws a human readable error message if not
• The CLI now checks whether jvmmon or jcmd is in the application container and throws a human readable error message if not
• More detailed success and error messages (e.g., when certain preconditions are not

Breaking changes:

• Previously, heap dumps were sent to stdout and could be redirected to a local file via >. By default heap dumps are no longer redirected to stdout and not stored in the application container. If a heap dump should be forwarded to the local machine use --local-dir instead.

2.0.0

Added support the SAP Java Buildpack. Kudos to @ScheererJ :-)

1.1.0

Extend container-side command to deal with corner cases that prevent creation
of heap dump and that do not cause jmap to fail properly:

If there is not enough space on the filesystem to write the dump, jmap will
create a file with size 0, output something about not enough space left on
device and exit with status code 0.
If the heap dump file already exists, jmap will output something about the
file already existing and exit with status code 0.
Now the command will check that:

jmap exited with status code 0 (so far always been the case, but you never know)
the heap dump file exists and has size > 0
Fail otherwise, outputting on STDERR of cf java the output of jmap

1.0.0

Initial release