1765683 - PI Java stack doesn't start due to RFC Adapter service | SAP Knowledge Base Article

SAP Knowledge Base Article - Preview

1765683 - PI Java stack doesn't start due to RFC Adapter service

Symptom

  • The Java stack in your PI system is not starting.
     
  • The default trace files and thread dumps show that there is an issue with the RFC Adapter service starting (com.sap.aii.adapter.rfc.svc).
     
  • You see the following entry in the thread dumps:
    • Thread 'Service Runner [com.sap.aii.adapter.rfc.svc]', process 'server1', index '70'
      "Service Runner [com.sap.aii.adapter.rfc.svc]" Id=85 RUNNING cpu=2000.51 ms (system=37.65 / user=1962.85)  allocated=50219048 B
        Thread is running:
        at com.sap.mw.rfc.driver.CpicDriver.nativeCpic_coxread([BI[B[I)I(Native Method)
        at com.sap.mw.rfc.driver.CpicDriver.cpic_coxread([BI[B[I)I(CpicDriver.java:992)
        at com.sap.mw.rfc.driver.CpicDriver.coxread([BI[II)I(CpicDriver.java:229)
        at com.sap.mw.rfc.driver.RfcTypeDirectCpic.read([BI[I)I(RfcTypeDirectCpic.java:38)
        at com.sap.mw.rfc.engine.RfcIoOpenCntl.ab_rfcread([BII)I(RfcIoOpenCntl.java:304)
        at com.sap.mw.rfc.engine.RfcGet.rfcget_gethead(Lcom.sap.mw.rfc.engine.RfcIoOpenCntl;[B)V(RfcGet.java:323)
        at com.sap.mw.rfc.engine.RfcGet.rfcget_run(Lcom.sap.mw.rfc.engine.RfcIoOpenCntl;IILcom.sap.mw.rfc.engine.RfcGetInfo;)I(RfcGet.java:53)
        at com.sap.mw.rfc.engine.RfcGet.ab_rfcget(Lcom.sap.mw.rfc.engine.RfcIoOpenCntl;ILcom.sap.mw.rfc.engine.RfcGetInfo;)I(RfcGet.java:27)
        at com.sap.mw.rfc.engine.RfcRcv.ab_rfcreceive(Lcom.sap.mw.rfc.engine.RfcIoOpenCntl;[Lcom.sap.mw.rfc.api.IRfcParameter;[Lcom.sap.mw.rfc.api.IRfcParameter;[Lcom.sap.mw.rfc.api.IRfcTable;)V(RfcRcv.java:39)
        at com.sap.mw.rfc.api.RfcApi.RfcReceive(J[Lcom.sap.mw.rfc.api.IRfcParameter;[Lcom.sap.mw.rfc.api.IRfcParameter;[Lcom.sap.mw.rfc.api.IRfcTable;)V(RfcApi.java:1005)
        at com.sap.mw.rfc.api.RfcApi.RfcOpen(Lcom.sap.mw.rfc.api.RfcOptions;)J(RfcApi.java:792)
        at com.sap.mw.jco.MiddlewareJRfc$Client.connect(Lcom.sap.mw.jco.JCO$Client;Ljava.lang.String;)V(MiddlewareJRfc.java:985)
        at com.sap.mw.jco.JCO$Client.connect()V(JCO.java:3435)
        at com.sap.aii.adapter.rfc.core.repository.RfcRepository.<init>(Lcom.sap.aii.adapter.rfc.core.config.RfcConfig;Ljava.lang.String;)V(RfcRepository.java:78)
        at com.sap.aii.adapter.rfc.core.RfcPool.initializePool(Lcom.sap.aii.adapter.rfc.core.config.RfcConfig;Ljava.lang.String;Z)V(RfcPool.java:124)
        at com.sap.aii.adapter.rfc.core.client.RfcClientPool.<init>(Lcom.sap.aii.adapter.rfc.core.config.RfcClientConfig;Ljava.lang.String;Z)V(RfcClientPool.java:153)
    •   at com.sap.aii.adapter.rfc.core.client.RfcClientPool.<init>(Lcom.sap.aii.adapter.rfc.core.config.RfcClientConfig;)V(RfcClientPool.java:123)
        at com.sap.aii.adapter.rfc.core.RfcRuntimeManager.channelAdded(Lcom.sap.aii.af.service.cpa.Channel;)V(RfcRuntimeManager.java:1008)
        at com.sap.aii.adapter.rfc.core.RfcRuntimeManager.channelInit()V(RfcRuntimeManager.java:882)
        at com.sap.aii.adapter.rfc.core.RfcRuntimeManager.startup()V(RfcRuntimeManager.java:133)
        at com.sap.aii.adapter.rfc.service.RfcService.start(Lcom.sap.engine.frame.ApplicationServiceContext;)V(RfcService.java:130)
        at com.sap.engine.core.service630.container.ServiceRunner.startFrame(Lcom.sap.engine.frame.ApplicationServiceFrame;)V(ServiceRunner.java:155)
        at com.sap.engine.core.service630.container.ServiceRunner.startService(Z)V(ServiceRunner.java:113)
        at com.sap.engine.core.service630.container.ServiceRunner.run()V(ServiceRunner.java:60)
        at com.sap.engine.frame.core.thread.Task.run()Ljava.lang.Object;(Task.java:73)
        at com.sap.engine.core.thread.impl5.SingleThread.execute()V(SingleThread.java:175)
        at com.sap.engine.core.thread.impl5.SingleThread.run()V(SingleThread.java:274)
       
  • In the std_serverX files you can see:
    Timed out services
    Service [com.sap.aii.adapter.rfc.svc] > [currently starting]
    Timed out services

Read more...

Environment

  • PI Release Independent
  • SAP NetWeaver
  • SAP Process Integration

Product

SAP NetWeaver all versions ; SAP Process Integration all versions

Keywords

Process Integration 7.0, PI 7.0, PI 7.01, PI 7.02, Process Integration 7.10, PI 7.10, Process Integration 7.11, PI 7.11, Process Integration 7.30, PI 7.30, Process Integration 7.31, PI 7.31, Process Orchestration 7.40, PI 7.40, PO 7.40, Process Orchestration 7.50, PI 7.50, PO 7.50, NetWeaver, XI, AEX, com.sap.aii.af.rfc.core.RfcRuntimeManager, starting framework, com.sap.conn.rfc.driver.CpicDriver, sap.com/com.sap.aii.adapter.rfc.svc, restart, reboot , KBA , BC-XI-CON-RFC , RFC Adapter , BC-XI-CON-AFW , J2EE Adapter Framework , 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.