The Netweaver AS Java crashes with an OutOfMemoryError while performing BPM Real-Time Reporting with Visual Composer
- On 7.20-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
A heap dump will be generated automatically if the SAP JVM (Java Virtual Machine) is configured to generate heap dumps with this parameter:
A heap dump can be manually generated and analyzed per SAP Note 1883568 - How to self analyze a Heap Dump using MAT
Heap analysis will show this similar type of result:
<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. The memory is accumulated in one instance of "com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.QueryView" loaded by "sap.com/com.sap.ip.bi.bics"
- Business Information Warehouse
- SAP Netweaver Application Server Java
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.