The sapjvm buildpack tries to store the heap dumps for customers when -XX:+HeapDumpOnOutOfMemory error is set. Since the customer has no access to the shared file store (basically a nfs share mounted in the VM) and local disk space is very limited, the idead was to stream the heap dump to the object store.
Unfortunately, in JDK 25 and higher, a segmented heap dump is used which prevents piping directly to a named pipe without needing additional disk space. There should be a method to get the old behavior of not needing additional disk space.
Additionally, since the upload to the object store is relatively slow, methods to make the heap dump smaller should be explored.
The sapjvm buildpack tries to store the heap dumps for customers when -XX:+HeapDumpOnOutOfMemory error is set. Since the customer has no access to the shared file store (basically a nfs share mounted in the VM) and local disk space is very limited, the idead was to stream the heap dump to the object store.
Unfortunately, in JDK 25 and higher, a segmented heap dump is used which prevents piping directly to a named pipe without needing additional disk space. There should be a method to get the old behavior of not needing additional disk space.
Additionally, since the upload to the object store is relatively slow, methods to make the heap dump smaller should be explored.