One Managed Server that is part of a large domain throws java.lang.out of Memory error (OOM)
occasionally.
You have been monitoring this server with the jvisualVM tool but that didn’t help because the issue
occurs infrequently and not a specific scenario. So you decided to force the server to dump the
heap memory as soon as an OOM gets thrown in order to analyze the dump file later.
How do you modify the Java HotSpot Startup command to enable this feature and save the dump
in the directory D:\hprof-dumps\?
A.
Add –xx:+DumpHeaponoutofmemory-xx:Dumppath=D:\hprof.
B.
Add-xx:+HeapDumponoutofmemoryError-xx:Heapdumppath=D:\hprof-dumps.
C.
Add-xx:+DumpHeaponoutofmemoryError-xx:Heappath=D:\hprof-dump.
D.
Add-xx:+HeapdumponoutofMemory-xx:HeapDumppath=D:\hprof-dumps.
E.
Add-xx:+HeapDumponoutofMemoryError-xx:Dumppath=D\hprof-dumps.
F.
Add-xx:+HeapDumponoutofMemoryExecepttion-xx:HeapDumppath=D:\hprof-dumps.
B is correct
I confirm B is correct answer
It depends
B
B http://blog.ragozin.info/2011/09/hotspot-jvm-garbage-collection-options.html