Symptom
AS Java system restarts and in server logs "exit code 666" can be seen. Heap Dump is generated. After parsing the heap dump (by KBA: 1883568 - How to self analyze a Heap Dump using MAT) the leap report shows IIOP service related suspects. See examples:
[...]
The class "com.sun.corba.se.impl.javax.rmi.CORBA.Util", loaded by "<system class loader>", occupies 504,608,048 (12.36%) bytes. The memory is accumulated in one instance of "com.sun.corba.se.impl.util.IdentityHashtableEntry[]" loaded by "<system class loader>".
[...]
[...]
18,906 instances of "com.sap.engine.services.iiop.server.IIOPGenericTie", loaded by "com.sap.engine.boot.loader.ResourceMultiParentClassLoader @ 0x7483cbad8" occupy 1,011,010,624 (25.22%) bytes. These instances are referenced from one instance of "com.sun.corba.se.impl.util.IdentityHashtableEntry[]", loaded by "<system class loader>"
[...]
Read more...
Environment
SAP NetWeaver Application Server Java
Product
Keywords
J2EE, NW Java, CORBA, NW AS Java, OOM, memory issue, exit code 666, 666, exit code, configtool, config tool , KBA , BC-JAS-COR-RMT , RMI, P4, CORBA, IIOP , BC-SRV-FP , Forms Processing , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.