If the AEM author instance is unstable with an OutOfMemoryError, which JVM parameter should you add to collect a heap dump?

If the AEM author instance is unstable with an OutOfMemoryError, which JVM parameter should you add to collect a heap dump?

• A. -XX:+HeapDumpOnOutOfMemoryError
• B. -XX:-PrintConcurrentLocks
• C. -XX:OnOutOfMemoryError='kill -3 %p'
• D. -XX:+PrintGCDetails

Answer: (A)

Collecting a heap dump at the moment an OutOfMemoryError occurs is essential for diagnosing memory issues, especially in a heavy-load environment like an AEM author instance. The JVM option -XX:+HeapDumpOnOutOfMemoryError tells the JVM to automatically create a heap dump when an OutOfMemoryError happens, capturing the objects in memory and their references so you can analyze what's consuming memory and why. You can pair this with -XX:HeapDumpPath to control where the dump is saved. The other options don’t generate a heap dump: one toggles lock logging, another runs a command on OOM (often used to trigger a thread dump or alert), and another prints GC details. So the best choice for automatic heap dump collection is -XX:+HeapDumpOnOutOfMemoryError.

Collecting a heap dump at the moment an OutOfMemoryError occurs is essential for diagnosing memory issues, especially in a heavy-load environment like an AEM author instance. The JVM option -XX:+HeapDumpOnOutOfMemoryError tells the JVM to automatically create a heap dump when an OutOfMemoryError happens, capturing the objects in memory and their references so you can analyze what's consuming memory and why. You can pair this with -XX:HeapDumpPath to control where the dump is saved. The other options don’t generate a heap dump: one toggles lock logging, another runs a command on OOM (often used to trigger a thread dump or alert), and another prints GC details. So the best choice for automatic heap dump collection is -XX:+HeapDumpOnOutOfMemoryError.