Last updated on JULY 08, 2016
Applies to:Oracle Agile PLM Framework - Version 220.127.116.11 and later
Information in this document applies to any platform.
***Checked for relevance on 17-JUN-2014***
The JVM (Java Virtual Machine) shares/allocates heap memory among all JVM threads. A Heap is the runtime data area where Java Class instances and arrays reside in. Once JVM start-ups (Agile PLM start-up), the Heap storage will be claimed and reclaimed by Garbage Collector automatically. So a Heap Dump is a reflection of current Java Heap memory allocation, telling us how much memory is consumed by each Java Class instance or variable. We collect Heap Dump when we see the OutOfMemory error, or notice the memory usage on Agile Application Server goes higher and higher.
There are two ways to output the Heap Dump data (how the memory is allocated to Java objects), the event of OutOfMemoryError and Manual trigger, like the Ctrl+Break on the command console where the Java application runs.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms