1515139 - BI data access queries causing OOM crashes in AS JAVA environment

• On 7.10-7.31 systems, in the work directory of the central dialog instance, the dev_jstart will contain an exit code of 666.  The std_server<n>.out log will contain java.lang.OutOfMemoryError or Out of memory or JLaunchIExitJava: exit hook is called (rc=666).  The dev_server<n>.out may contain entries such as LOG => SfCJavaVm: exit hook is called. (rc = 666)
  
  The server<n>/log/defaultTrace_nn.n.trc may contain entries such as:  The system is out of resources. Consult the following stack trace for details. java.lang.OutOfMemoryError: Java heap space
   
• On 6.40-7.02 systems,  we can see in the dev_jcontrol:  JLaunchIExitJava: exit hook is called (rc=666).
  In the std_server<n>.out logs: FATAL: Caught OutOfMemoryError! Node will exit with exit code666 java.lang.OutOfMemoryError

A heap dump will be generated automatically if the JVM (Java Virtual Machine) is configured to generate heap dumps with these parameters:

• -XX:+HeapDumpOnOutOfMemoryError (for Sun/SAP JVM)
• -Xdump:system:events=systhrow,filter=java/lang/OutOfMemoryError,request=exclusive+prepwalk (IBM JVM)

Depending a on the product and operating system you are using, a heap dump can be manually generated per SAP Notes:

1004255 - How to create a full HPROF heap dump of J2EE Engine on SUN/HP-UX
1259465 - How to get a heapdump which can by analyzed with MAT for IBM AIX
1263258 - IBM JDK 1.4.2 x86_64: How to get a proper heapdump for MAT
1289240 - How to deal with out of memory errors (NW 7.10-7.31)
1265455 - How can you generate a system dump for analysis using MAT?

Review SAP KBA 1883568 for information on downloading the memory analyzer and how to use it to parse a heap dump.

Heap analysis will show these similar type of results:

Sample a. <nnn> instances of "com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.QueryView", loaded by "sap.com/com.sap.ip.bi.bics" occupy (nnn,nnn,nnn) (20-70%) bytes.

Please note that in case you are performing BPM Real-Time Reporting with Visual Composer, the leak suspect is the same. For that scenario and resolution, review SAP
KBA 1848021.

Sample b. One instance of "java.util.ArrayList" loaded by "<system class loader>" occupies (nnn,nnn,nnn)(20-70%) bytes. The instance is referenced by com.sap.ip.bi.webapplications.ui.unifiedrendering.controls.SingleColumnLayout @ 0xd7de25c0 , loaded by
sap.com/com.sap.ip.bi.web.unifiedrendering". The memory is accumulated in one instance of "java.lang.Object[]" loaded by "<system classloader>".Keywords java.util.ArrayList java.lang.Object[] sap.com/com.sap.ip.bi.web.unifiedrendering
The thread is executing an HTTP Request to application"/irj", path"/portal/prtroot/com.sap.ip.bi.web.portal.integration.launcher"

Sample c. The thread com.sap.engine.core.thread.impl3.SingleThread @ 0x700000020df6638 SAPEngine_Application_Thread[impl:3]_39 keeps local variables with total size (nnn,nnn,nnn) (20-70%) bytes. The memory is accumulated in one instance of "com.sap.engine.core.thread .impl3.SingleThread" loaded by "com.sap.engine.boot.CoreClassLoader @0x700000020a2acc0".
The thread is executing an HTTP Request to application"/irj", path"/portal/prteventname/Navigate/prtroot/com.sap.ip.bi.web.portal.integration.launcher".at com.sap.ip.bi.export.office.impl.excel.ExcelHtmlDocument.writeOfficeHtmlDocumentToStream (Ljava/io/PrintWriter;Ljava/io/PrintWriter;) V (ExcelHtmlDocument.java:169(Compiled Code)) at com.sap.ip.bi.export.office.common.OfficeHtmlDocument.writeOfficeHtmlDocumentToByte(Ljava/lang/String;) [B (OfficeHtmlDocument.java:248) at com.sap.ip.bi.export.office.common.OfficeHtmlDocument.writeOfficeHtmlDocumentToByte()[B (OfficeHtmlDocument.java:265) at com.sap.ip.bi.export.office.impl.excel.MsExcelConverter.getBinaryContent()[B (MsExcelConverter.java:146)

Sample d. One instance of "com.sap.ip.bi.webapplications.techitems.contextmenu.ContextMenuItem" loaded by "sap.com/com.sap.ip.bi.web.items.contextmenu" occupies (nnn,nnn,nnn) (10-70%) bytes. The memory is accumulated in one instance of "char[]" loaded by "<system class loader>" 
and/or 
one instance of "com.sap.ip.bi.webapplications.ui.container.group.standard.GroupItem" loaded by "sap.com/com.sap.ip.bi.web.items.container" occupies (nnn,nnn,nnn) (10-70%) bytes. The memory is accumulated in one instance of "char[]" loaded by "<system class loader>"
and/or
(nn) instances of "com.sap.ip.bi.util.builder.bi.BiStringBuilder", loaded by "sap.com/com.sap.ip.bi.base" occupy (nnn,nnn,nnn) (10-70%) bytes.

Read more...

• Business Information Warehouse
   
• SAP Netweaver Apllication Server Java

SAP NetWeaver 2004 ; SAP NetWeaver 7.0 ; SAP NetWeaver 7.3 ; SAP NetWeaver Application Server for Java 7.1 ; SAP NetWeaver Application Server for Java 7.2 ; SAP enhancement package 1 for SAP NetWeaver 7.0 ; SAP enhancement package 1 for SAP NetWeaver 7.3 ; SAP enhancement package 1 for SAP NetWeaver Application Server for Java 7.1 ; SAP enhancement package 2 for SAP NetWeaver 7.0 ; SAP enhancement package 3 for SAP NetWeaver 7.0

OutOfMemory, OutOfMemoryError, short dumps, BI reports, BI exports, OOM, out of memory, 666, webapplications, JDK, JVM, BICS, safety bell, , KBA , kde , BW-BEX-ET-WJR , BEx Web Java Runtime , Problem