Most of the times the size of heap dump from a production server will be averaging from 4GB to 6GB. Our default heap settings will not be enough to load those heap dump in any of the analyzer tools.
Before loading the analyzer we can set the maximum heap size to accommodate the dump file size using the jvm argument -Xmx. This one specifies the maximum size, in bytes, of the memory allocation pool and must be greater than 2MB. Append the letter k or K to indicate kilobytes, or m or M to indicate megabytes. The default value is 64MB
Suppose you are using jca457.jar as analyzer tool and your heap size is very less to accommodate the heap dump, you can use "
In case of eclipse plugin or memory analyzer tool from IBM you can set these values in the ini file associated with the executable.
Before loading the analyzer we can set the maximum heap size to accommodate the dump file size using the jvm argument -Xmx. This one specifies the maximum size, in bytes, of the memory allocation pool and must be greater than 2MB. Append the letter k or K to indicate kilobytes, or m or M to indicate megabytes. The default value is 64MB
Suppose you are using jca457.jar as analyzer tool and your heap size is very less to accommodate the heap dump, you can use "
java -jar -Xmx6000M jca457.jar" to set the heap size to 6000MB (You need to have enough space in RAM to allocate the heap size) while loading the analyzer.In case of eclipse plugin or memory analyzer tool from IBM you can set these values in the ini file associated with the executable.
No comments:
Post a Comment