SAP Knowledge Base Article - Preview

2757080 - IDoc_AAE messages hang in To Be Delivered status

Symptom

  • You have a Process Orchestration (PO) system which is using the IDoc_AAE Adapter 
  • You notice that interfaces using this Adapter type encounter problems during message processing
  • This will happen after a recent SPS and Kernel update to the system
  • This can manifest in different ways and be visible in different locations but mainly messages will hang in status Delivering/To Be Delivered
  • Backlogs will also be visible in the messaging queues - see note 1662269 How to Monitor the PI Adapter Framework queues or use the XPI Inspector trace to monitor these queues
  • If you take Java Thread Dumps, you will find threads with a stack trace similar to below: 

    "Managed_Application_Thread_89" tid=0xb8256ad345 runnable cpu=978.34 ms allocated memory=1023987 B file i/o:0/0 B net i/o:223/511 B files opened:0 socks opened:0 nid=0x27b0 prio=-1
    at com.sap.conn.rfc.driver.CpicDriver.nativeCpic_coxread([BI[B[I)I(Native Method)
    at com.sap.conn.rfc.driver.CpicDriver.cpic_coxread(I[B[I)I(CpicDriver.java:649)
    at com.sap.conn.rfc.driver.CpicDriver.coxread([BI[II)I(CpicDriver.java:210)
    at com.sap.conn.rfc.driver.RfcTypeDirectCpic.read([BI[I)I(RfcTypeDirectCpic.java:42)
    - locked<0x768d42f32> (a com.sap.conn.rfc.driver.RfcTypeDirectCpic)
    at com.sap.conn.rfc.engine.RfcIoOpenCntl.ab_rfcread([BII)I(RfcIoOpenCntl.java:646)
    at com.sap.conn.rfc.engine.RfcGetImp.rfc_readData(Lcom.sap.conn.rfc.engine.RfcGetData_Input;[BII)V(RfcGetImp.java:254)
    at com.sap.conn.rfc.engine.RfcGetImp.rfc_getdata(Lcom.sap.conn.rfc.engine.RfcGetData_Input;Lcom.sap.conn.rfc.engine.RfcValInfo;II)V(RfcGetImp.java:217)
    at com.sap.conn.rfc.engine.RfcGetImp.ab_rfcvalue(Lcom.sap.conn.rfc.engine.RfcIoOpenCntl;Lcom.sap.conn.rfc.engine.RfcValInfo;I)V(RfcGetImp.java:171)
    at com.sap.conn.rfc.engine.RfcImp.ab_rfctcontLZ(Lcom.sap.conn.rfc.engine.RfcIoOpenCntl;Lcom.sap.conn.rfc.engine.RfcGetInfo;IZ)V(RfcImp.java:196)
    at com.sap.conn.rfc.engine.RfcGet.ab_rfcget(Lcom.sap.conn.rfc.engine.RfcIoOpenCntl;Lcom.sap.conn.rfc.engine.RfcGet$RfcGetState;Lcom.sap.conn.rfc.engine.RfcGetInfo;)I(RfcGet.java:220)
    at com.sap.conn.rfc.engine.RfcRcv.ab_rfcreceive(Lcom.sap.conn.rfc.engine.RfcIoOpenCntl;[Lcom.sap.conn.rfc.api.IRfcParameter;[Lcom.sap.conn.rfc.api.IRfcParameter;[Lcom.sap.conn.rfc.api.IRfcParameter;[Lcom.sap.conn.rfc.api.IRfcTable;Lcom.sap.conn.jco.rt.RepositoryProvider;)V(RfcRcv.java:35)
    at com.sap.conn.rfc.engine.RfcIoOpenCntl.RfcReceive([Lcom.sap.conn.rfc.api.IRfcParameter;[Lcom.sap.conn.rfc.api.IRfcParameter;[Lcom.sap.conn.rfc.api.IRfcTable;Lcom.sap.conn.jco.rt.RepositoryProvider;)V(RfcIoOpenCntl.java:1974)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcClient.execute(Lcom.sap.conn.jco.rt.ClientConnection;Ljava.lang.String;Lcom.sap.conn.jco.rt.DefaultParameterList;Lcom.sap.conn.jco.rt.DefaultParameterList;Lcom.sap.conn.jco.rt.DefaultParameterList;Lcom.sap.conn.jco.rt.DefaultParameterList;ZLcom.sap.conn.jco.AbapClassException$Mode;)V(MiddlewareJavaRfc.java:1977)
    at com.sap.conn.jco.rt.ClientConnection.execute(Ljava.lang.String;Lcom.sap.conn.jco.rt.DefaultParameterList;Lcom.sap.conn.jco.rt.DefaultParameterList;Lcom.sap.conn.jco.rt.DefaultParameterList;Lcom.sap.conn.jco.rt.DefaultParameterList;ZLcom.sap.conn.jco.AbapClassException$Mode;)V(ClientConnection.java:1160)
    at com.sap.conn.jco.rt.ClientConnection.execute(Lcom.sap.conn.jco.JCoFunction;Ljava.lang.String;Ljava.lang.String;Lcom.sap.conn.jco.rt.RepositoryProvider;)V(ClientConnection.java:989)
    at com.sap.conn.jco.rt.ClientConnection.execute(Lcom.sap.conn.jco.JCoFunction;Lcom.sap.conn.jco.rt.RepositoryProvider;)V(ClientConnection.java:971)
    at com.sap.conn.jco.rt.ConnectionManager.internalExecute(Lcom.sap.conn.jco.JCoFunction;Lcom.sap.conn.jco.JCoDestination;Z)V(ConnectionManager.java:505)
    at com.sap.conn.idoc.jco.rt.SAPRepository$ConnectionProvider.execute(Lcom.sap.conn.jco.JCoFunction;)V(SAPRepository.java:1717)
    at com.sap.conn.idoc.jco.rt.SAPRepository$ConnectionProvider.access$100(Lcom.sap.conn.idoc.jco.rt.SAPRepository$ConnectionProvider;Lcom.sap.conn.jco.JCoFunction;)V(SAPRepository.java:1665)
    at com.sap.conn.idoc.jco.rt.SAPRepository.queryRootSegmentMetaData40(Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)Lcom.sap.conn.idoc.IDocSegmentMetaData;(SAPRepository.java:1246)
    at com.sap.conn.idoc.jco.rt.SAPRepository.queryRootSegmentMetaData(Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)Lcom.sap.conn.idoc.IDocSegmentMetaData;(SAPRepository.java:1113)
    at com.sap.conn.idoc.jco.rt.SAPRepository.getRootSegmentMetaData(Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)Lcom.sap.conn.idoc.IDocSegmentMetaData;(SAPRepository.java:880)
    - locked<0x76b336e48> (a java.lang.Object)
    at com.sap.conn.idoc.rt.DefaultIDocDocument.<init>(Ljava.lang.String;Lcom.sap.conn.idoc.IDocRepository;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)V(DefaultIDocDocument.java:114)...


Read more...

Environment

  • SAP NetWeaver 7.4
  • SAP NetWeaver 7.5
  • SAP Kernel 

Product

SAP NetWeaver 7.4 ; SAP NetWeaver 7.5

Keywords

Process Orchestration 7.4, PI 7.4, PO 7.4, Process Orchestration 7.5, PI 7.5, PO 7.5, XI, AEX, cloned inboundRA, Resource Adapter, Gateway, RFC Destination, JCO, XI_IDOC_DEFAULT_DESTINATION, preload metadata, read metadata, backend R/3 , KBA , BC-XI-CON-IDO , Idoc Adapter J2EE , BC-CST-GW , Gateway/CPIC , Problem

About this page

This 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.