SAP Knowledge Base Article - Preview

3388783 - OOM caused by large sized IDoc processing

Symptom

  • You are using an IDoc sender adapter and you see JVM crashing with OOM errors;
  • Leak suspect report shows the below problem suspect:

    The thread com.sap.engine.core.thread.execution.CentralExecutor$SingleThread @ 0x753190a40 Managed_Application_Thread_69 keeps local variables with total size 3,270,542,944 (80.34%) bytes.

    The memory is accumulated in one instance of "com.sap.engine.core.thread.execution.CentralExecutor$SingleThread" loaded by "system:Kernel".

  • Stacktrace shows the below logs:Managed_Application_Thread_69
      at com.sap.conn.jco.rt.AbstractRecord.decodeCHAR(I)Ljava/lang/String; (AbstractRecord.java:5460)
      at com.sap.conn.jco.rt.AbstractRecord.getString(I)Ljava/lang/String; (AbstractRecord.java:1563)
      at com.sap.conn.idoc.jco.rt.JCoIDocDocument.createIDocDocument(Lcom/sap/conn/idoc/IDocRepository;Lcom/sap/conn/idoc/jco/rt/RawTable;ILcom/sap/conn/idoc/jco/rt/RawTable;IZLjava/lang/String;Z)Lcom/sap/conn/idoc/jco/rt/JCoIDocDocument; (JCoIDocDocument.java:252)
      at com.sap.conn.idoc.jco.rt.JCoIDocRuntime.createIDocDocumentListArray(Lcom/sap/conn/idoc/IDocRepository;Lcom/sap/conn/idoc/jco/rt/RawTable;Lcom/sap/conn/idoc/jco/rt/RawTable;ZLjava/lang/String;Z)[Lcom/sap/conn/idoc/jco/rt/JCoIDocDocumentList; (JCoIDocRuntime.java:95)
      at com.sap.mw.jco.jra.idoc.JRAIDocRuntime.createIDocDocumentListArray(Lcom/sap/conn/idoc/IDocRepository;Lcom/sap/conn/idoc/jco/rt/RawTable;Lcom/sap/conn/idoc/jco/rt/RawTable;ZLjava/lang/String;)[Lcom/sap/conn/idoc/jco/rt/JCoIDocDocumentList; (JRAIDocRuntime.java:147)
      at com.sap.mw.jco.jra.idoc.JRAIDocExtension$IDocMessageHandler.getIDocDocumentListArrayFromRequest(Lcom/sap/conn/jco/JCoRequest;Lcom/sap/conn/jco/server/JCoServerContext;Lcom/sap/mw/jco/jra/IDocMessageListener;)[Lcom/sap/conn/idoc/IDocDocumentList; (JRAIDocExtension.java:174)
      at com.sap.mw.jco.jra.idoc.JRAIDocExtension$IDocMessageHandler.onMessage(Ljava/lang/Object;Lcom/sap/conn/jco/JCoRequest;Ljava/lang/String;Ljava/util/Properties;Lcom/sap/conn/jco/server/JCoServerContext;)V (JRAIDocExtension.java:107)
      at com.sap.mw.jco.jra.JRA$ReaderThread.sendDirectToMdb(Lcom/sap/conn/jco/server/JCoServerContext;Lcom/sap/conn/jco/JCoRequest;Ljava/util/Properties;Ljava/io/PrintWriter;Ljava/lang/String;)V (JRA.java:8004)
      at com.sap.mw.jco.jra.JRA$ReaderThread.sendAsynchRequest(Lcom/sap/conn/jco/server/JCoServerContext;Lcom/sap/conn/jco/JCoRequest;Ljava/lang/String;)V (JRA.java:7951)
      at com.sap.mw.jco.jra.JRA$ReaderThread.handleInternalRequest(Lcom/sap/conn/jco/server/JCoServerContext;Lcom/sap/conn/jco/JCoRequest;Lcom/sap/conn/jco/JCoResponse;Ljavax/security/auth/login/LoginContext;)V (JRA.java:8335)
      at com.sap.mw.jco.jra.JRA$ReaderThread.handleRequest(Lcom/sap/conn/jco/server/JCoServerContext;Lcom/sap/conn/jco/JCoRequest;Lcom/sap/conn/jco/JCoResponse;)V (JRA.java:8130)
      at com.sap.conn.jco.rt.DefaultServerWorker$RequestDispatcher.handleRequest(Lcom/sap/conn/jco/server/JCoServerContext;Lcom/sap/conn/jco/JCoFunction;)Lcom/sap/conn/jco/server/JCoServerRequestHandler; (DefaultServerWorker.java:1130)
      at com.sap.conn.jco.rt.DefaultServerWorker$RequestDispatcher.handleRequest(Lcom/sap/conn/jco/server/JCoServerContext;Lcom/sap/conn/jco/JCoFunction;)Ljava/lang/Object; (DefaultServerWorker.java:1064)
      at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(Lcom/sap/conn/jco/JCoFunction;)V (DefaultServerWorker.java:147)
      at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(Lcom/sap/conn/jco/rt/ServerWorker;Ljava/lang/String;)V (MiddlewareJavaRfc.java:3644)
      at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(Lcom/sap/conn/rfc/engine/RfcIoOpenCntl;Lcom/sap/conn/jco/rt/ServerWorker;)V (MiddlewareJavaRfc.java:3104)
      at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(Lcom/sap/conn/rfc/engine/RfcIoOpenCntl;Lcom/sap/conn/rfc/data/ARFCSDATA;ILcom/sap/conn/rfc/data/ARFCSSTATE;Lcom/sap/conn/jco/rt/DefaultServerWorker;)V (MiddlewareJavaRfc.java:2941)
      at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(Lcom/sap/conn/jco/rt/DefaultServerWorker;)V (MiddlewareJavaRfc.java:2835)
      at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(Lcom/sap/conn/jco/rt/ServerWorker;)V (MiddlewareJavaRfc.java:2631)
      at com.sap.conn.jco.rt.DefaultServerWorker.dispatch()V (DefaultServerWorker.java:274)
      at com.sap.conn.jco.rt.DefaultServerWorker.loop()V (DefaultServerWorker.java:362)
      at com.sap.conn.jco.rt.DefaultServerWorker.run()V (DefaultServerWorker.java:231)
      at com.sap.mw.jco.jra.JRA$ReaderThread.run()V (JRA.java:9016)
      at com.sap.engine.services.connector.jca15.work.TaskImpl.run()V (TaskImpl.java:245)
      at com.sap.engine.core.thread.execution.Executable.run(Z)V (Executable.java:122)
      at com.sap.engine.core.thread.execution.Executable.run()V (Executable.java:101)
      at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run()V (CentralExecutor.java:328)


Read more...

Environment

  • SAP Process Integration
  • SAP Process Orchestration

Product

SAP NetWeaver Process Integration, secure connectivity add-on 1.0

Keywords

IDoc sender adapter, IDoc_AAE, OOM, Out of memory, com.sap.engine.core.thread.execution.CentralExecutor$SingleThread, com.sap.conn.idoc.jco.rt.JCoIDocDocument.createIDocDocument. , KBA , BC-XI-CON-IDO , Idoc Adapter J2EE , 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.