Showing results for 
Show  only  | Search instead for 
Did you mean: 

Dynatrace analysis server itself out of memory


Hi Dynatrace experts,

When I analyzed a memory dump with used memory 7.67 GB and processed memory of 16.03 GB, I always got unknown error and the analysis stop. I set the max memory of Dynatrace analysis memory to 13GB. The total memory I have for the analysis server is 16145 MB. When looked into the analysis server log file, I found that the analysis server itself was out of memory.

Does the analysis server use processed memory to calculate? If so, why is process memory is so large? Dynatrace indicates that there is a potential native memory leak. I am not certain how relevant the warning is in regard to the issue we have in the analysis server.

Is there a work around?



2018-02-24 20:45:06 WARNING [MemoryDumpPostProcessor] error while dominator calculation: com.dynatrace.diagnostics.server.interfaces.memory.MemoryDumpPostProcessor a:830
java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(
at com.dynatrace.diagnostics.server.interfaces.memory.analysis.utils.IntStack.a(SourceFile:105)
at com.dynatrace.diagnostics.server.interfaces.memory.analysis.utils.IntStack.push(SourceFile:76)
at com.dynatrace.diagnostics.server.interfaces.memory.dominators.DominatorTreeCalculator.b(SourceFile:776)
at com.dynatrace.diagnostics.server.interfaces.memory.dominators.DominatorTreeCalculator.calcDominators(SourceFile:302)
at com.dynatrace.diagnostics.server.interfaces.memory.MemoryDumpPostProcessor.a(SourceFile:749)
at com.dynatrace.diagnostics.server.interfaces.memory.MemoryDumpPostProcessor.postProcessMemoryDump(SourceFile:337)
at com.dynatrace.diagnostics.oopAnalyzer.OOPAnalyzer$
at com.dynatrace.diagnostics.oopAnalyzer.OOPAnalyzer$

2018-02-24 20:45:06 WARNING [OOPAnalyzerWorkerThread] Error while post-processing memory dump: Unknown error while calculating dominators
2018-02-24 20:45:08 INFO [OOPAnalyzer] Cleaning-up data of Openlane Production/20180224094259_0.memdump
2018-02-24 20:46:46 INFO [OOPAnalyzer] Successfully got request for post-processing dump: Openlane Production/20180224031137_0.memdump
2018-02-24 20:46:46 INFO [OOPAnalyzer] Required Memory: 8700 MB, number of objects=209113988
2018-02-24 20:46:46 INFO [OOPAnalyzerProtocol35] retrieving file /home/atc/tools/dynaTrace/dynatrace-6.5/server/sessions/stored/Openlane Production/20180224031137_0.memdump/15195340069173841194162578822225.req
2018-02-24 20:46:46 INFO [OOPAnalyzerProtocol35] retrieving file /home/atc/tools/dynaTrace/dynatrace-6.5/server/sessions/stored/Openlane Production/20180224031137_0.memdump/imap.dtm
2018-02-24 20:46:47 INFO [OOPAnalyzerProtocol35] retrieving file /home/atc/tools/dynaTrace/dynatrace-6.5/server/sessions/stored/Openlane Production/20180224031137_0.memdump/main.dtm
2018-02-24 20:46:47 INFO [OOPAnalyzerProtocol35] retrieving file /home/atc/tools/dynaTrace/dynatrace-6.5/server/sessions/stored/Openlane Production/20180224031137_0.memdump/20180224031137_0.memdump.raw



Hello Ronald,

The amount of memory required for post-processing leak analysis memory snapshots mainly depends on the number of objects on the heap. For fully cached post-processing, required memory equals the heap size of the application for which the snapshot was taken. Although post-processing with less memory is possible, running with less than full-cache memory is not recommended.

Before starting the AppMon Memory Analysis Server, adjust the memory settings in the main configuration file dtanalysisserver.ini. Set the option -Xmx to the maximum heap size of applications + 25% to analyze.