3721760 - SAP PI/PO facing Frequent/Recurring OutOfMemory (OOM) issue

• SAP Process Integration/Process Orchestration application server nodes shut down and restart daily / frequently / recurringly due to OutOfMemory (OOM) errors
• JVM heap memory exhaustion is observed during runtime.
• OOM dump files(OOM.hprof) are generated leading to system instability
• Need to know why the OOM(s) are generating and what is cause of OOM files generation
• Guidance on how to overcome OOM issues in SAP PI/PO
• The Leak Suspect Report indicates high memory consumption with significant stack traces and local variables. The memory accumulation can typically be observed in the following patterns, keywords:
  
  • byte[x,xxx,xxx,xxx]
    char[x,xxx,xxx,xxx]
    byte[]
    char[]
    java.util.Arrays.copyOf
    java.lang.Object[]
    XIMessage
    
    x,xxx,xxx,xxx defines the number of bytes/ memory size in bytes/ payload size.
    

    In some situations, memory is heavily retained by classloader-related objects, 
    for example:
    instance of byte[] loaded by <system class loader> occupies x,xxx,xxx,xxx (<percentage>%) bytes
    com.sap.engine.boot.loader.ResourceMultiParentClassLoader @ <Thread ID>, occupying a significant portion (<percentage>%) of the heap memory

• dev_jstart contains exit code 666.
• std_serverN.out contains java.lang.OutOfMemoryError or Out of memory (N is the number of server node)

• SAP Process Integration 
• SAP NetWeaver

PI, PO, OutOfMemory, 666, frequent, recurring, daily, OOM, heap exhaustion, large, payload, restart, large message handling, JVM heap, server restart, memory leak, byte, char, exit code [666], OOM, crash. , KBA , SV-PERF-PI , SAP Process Integration (PI) related performance issues , BC-XI-CON-MSG , Messaging System , BC-JAS-COR , Enterprise Runtime, Core J2EE Framework , BC-JAS-MAT , Memory Analysis Tools , SV-PERF-JAS , SAP NetWeaver AS Java related performance issues , BC-XI-CON , Connectivity , Problem