1883568 - How to Self Analyze a Heap Dump Using MAT

SAP Knowledge Base Article

 

  1883568 - How to self analyze a Heap Dump using MAT Version   4     Validity: 13.07.2013 - active  

 

Language   English

Symptom The SAP NetWeaver Application Server Java crashed due to an unknown reason, and in the std_serverX or dev_serverX files you see at least one of the following messages: l

l

l

FATAL: Caught OutOfMemoryError! Node will exit with exit code 666java.lang.OutOfMemoryError   JLaunchIExitJava: exit hook is called (rc = 666)   java.lang.OutOfMemoryError: Java heap space

Environment SAP NetWeaver Application Server Java

Resolution Download the Eclipse Memory Analyzer tool. It will be used to parse the Heap Dump file on your own machine. Locate the Heap Dump, which is usually on the folder /usr/sap///j2ee/cluster/server/ where N is the server node number. The file extension can be *.dmp and *.hprof. If you already have a heap dump file into the above place proceed to Step 1. If you don't have a Heap Dump file, follow SAP Note 1004255 and  setup the system to generate it in the next occurrence.   With the Heap Dump, proceed as follows: 1. Open it using Eclipse Memory Analyzer:

     2. Click on Parse. While parsing you can see the progress:

     3. Select the format of the result. In most cases, the Leak Suspects Report will be enough.

     4. Open the Leak Suspects Report and check the results:

If the heap dump report show that the problematic application is your own custom code or another partner software, contact the responsible for  that application. If after checking the report and searching for notes you cannot find a solution, attach the Leak Suspects Report to the SAP message so a Support Engineer can analyze the results. The Leak Suspects Report is located on the same folder of the Heap dump. The screenshot below shows that:

  Considerations: l

l

Parsing a Heap Dump can be a memory consuming task. Doing that on the same server your productive or critical system is running is NOT advisable;    You can do that on a standalone machine in order to not affect your productive or critical system performance.

Keywords Exitcode, 666, OOM, crash, Out of Memory, Memory, Dump, Outage

Header Data Released On Release Status Component Other Components

13.07.2013 18:03:20 Released to Customer BC-JAS-COR Enterprise Runtime, Core J2EE Framework BC-JAS-MAT Memory Analysis Tools

Priority Normal Category How To Development Platform Java

Product Product SAP NetWeaver

Product Version SAP NetWeaver 2004 SAP NetWeaver 7.0 SAP NetWeaver 7.3 SAP NetWeaver 7.4 SAP enhancement package 1 for SAP NetWeaver 7.0 SAP enhancement package 1 for SAP NetWeaver 7.3 SAP enhancement package 2 for SAP NetWeaver 7.0 SAP enhancement package 3 for SAP NetWeaver 7.0 SAP NetWeaver Application Server for Java SAP NetWeaver Application Server for Java 7.1 SAP NetWeaver Application Server for Java 7.2 SAP enhancement package 1 for SAP NetWeaver Application Server f

References This document refers to: CSS SAP Notes 1289240   How to deal with out of memory errors 1004255   How to create a full HPROF heap dump of J2EE Engine 6.40/7.0 SAP Community Network Finding Memory Leaks with SAP Memory Analyzer External Hyperlink Automated Heap Dump Analysis: Finding Memory Leaks with One Click