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