Avoiding SAP JAVA hung situation in entire SAP landscape due to heap dump generation
Problem: java systems getting hanged due to heap dump generation in the path /usr/sap/ resulting in service disruption. Even with the file system alerts, the generation( which happens very fast) and size of the dump file is so big(5GB-10 GB), before BASIS team could act and move/delete the heap dump files the system does reaches the hung state(might sometime would require a restart as well).
Create a separate mount point like /usr/sap/dumps and point the dump generation in
that location rather than /usr/sap/<SID>. The size of the new file system could be 5-10 times the heap size(approx. 15-20 GB).
1.What parameters I need to tune?
2. How to get heap dump generated at will to see if the new heap dump files are getting generated in the new file system?