Java virtual machine jvm version 1.6.19 or later

HeapDumpOnOutOfMemoryError instructs the JVM to dump heap into physical file in case of OutOfMemoryError.

That's why JVM comes with some parameters which dump heap memory into a physical file which can be used later for finding out leaks: -XX:+HeapDumpOnOutOfMemoryError

It's a very critical scenario and very hard to replicate to troubleshoot the issue. It's very common for a large application to face out of memory error which, in turn, results in the application crash.

This behavior may create some performance bottleneck that's why it's always better not to play with this parameter in production. However, the problem is that one additional daemon thread is always used for monitoring system time in the background. Point to note here is that, there are two more JVM parameters available ( -XX:+PrintGCTimeStamps and -XX:+PrintGCDateStamps) which can be used to print date-wise timestamp in the GC log.ДЇor example, if we want to assign a maximum of 100 GC log files, each having a maximum size of 50 MB and want to store them in вЂ /home/user/log/' location, we can use below syntax: -XX:+UseGCLogFileRotation

GCLogFileSize specifies the max size of the file. NumberOfGCLogFiles denotes the max number of log files that can be written for a single application life cycle. UseGCLogFileRotation specifies the log file rolling policy, much like log4j, s4lj, etc.

Java virtual machine jvm version 1.6.19 or later