Hi all,
we have the following situation:
We use SAP PI for a RFC -> SAP PI -> SOAP scenario.
Once in a while our Basis needs to shut down the sender SAP system. It seems that the sender RFC channel looses registration on Gateway after some time. We get the following errors:
| Time | Message |
|---|---|
| 05.05.13 15:15:18 | Verarbeitungsfehler verursacht durch: com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Sun May 05 15:15:18 CEST 2013. This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds. Could not start server: Connect to SAP gateway failed Connection parameters: TPNAME=SAPXI_PRA GWHOST=x.x.x.x GWSERV=sapgw00 ERROR partner 'x.x.x.x:sapgw00' not reached TIME Sun May 5 15:15:18 201 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -10 MODULE nibuf.cpp LINE 4607 DETAIL NiBufIConnect: connection pending after 60000ms SYSTEM CALL connect ERRNO 55 ERRNO TEXT A connect operation on a socket is not complete. COUNTER 118 |
| 05.05.13 14:15:18 | Verarbeitungsfehler verursacht durch: com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Sun May 05 14:15:18 CEST 2013. This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds. Could not start server: Connect to SAP gateway failed Connection parameters: TPNAME=SAPXI_PRA GWHOST=x.x.x.x GWSERV=sapgw00 ERROR partner 'x.x.x.x:sapgw00' not reached TIME Sun May 5 14:15:18 201 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -10 MODULE nibuf.cpp LINE 4607 DETAIL NiBufIConnect: connection pending after 60000ms SYSTEM CALL connect ERRNO 55 ERRNO TEXT A connect operation on a socket is not complete. COUNTER 117 |
| 05.05.13 13:15:17 | Verarbeitungsfehler verursacht durch: com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Sun May 05 13:15:17 CEST 2013. This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds. Could not start server: Connect to SAP gateway failed Connection parameters: TPNAME=SAPXI_PRA GWHOST=x.x.x.x GWSERV=sapgw00 ERROR partner 'x.x.x.x:sapgw00' not reached TIME Sun May 5 13:15:17 201 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -10 MODULE nibuf.cpp LINE 4607 DETAIL NiBufIConnect: connection pending after 60000ms SYSTEM CALL connect ERRNO 55 ERRNO TEXT A connect operation on a socket is not complete. COUNTER 116 |
| 05.05.13 12:15:16 | Verarbeitungsfehler verursacht durch: com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Sun May 05 12:15:16 CEST 2013. This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds. Could not start server: Connect to SAP gateway failed Connection parameters: TPNAME=SAPXI_PRA GWHOST=x.x.x.x GWSERV=sapgw00 ERROR partner 'x.x.x.x:sapgw00' not reached TIME Sun May 5 12:15:16 201 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -10 MODULE nibuf.cpp LINE 4607 DETAIL NiBufIConnect: connection pending after 60000ms SYSTEM CALL connect ERRNO 55 ERRNO TEXT A connect operation on a socket is not complete. COUNTER 115 |
| 05.05.13 11:15:15 | Verarbeitungsfehler verursacht durch: com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Sun May 05 11:15:15 CEST 2013. This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds. Could not start server: Connect to SAP gateway failed Connection parameters: TPNAME=SAPXI_PRA GWHOST=x.x.x.x GWSERV=sapgw00 ERROR partner 'x.x.x.x:sapgw00' not reached TIME Sun May 5 11:15:15 201 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -10 MODULE nibuf.cpp LINE 4607 DETAIL NiBufIConnect: connection pending after 60000ms SYSTEM CALL connect ERRNO 55 ERRNO TEXT A connect operation on a socket is not complete. COUNTER 111 |
| 05.05.13 10:15:14 | Verarbeitungsfehler verursacht durch: com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Sun May 05 10:15:14 CEST 2013. This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds. Could not start server: Connect to SAP gateway failed Connection parameters: TPNAME=SAPXI_PRA GWHOST=x.x.x.x GWSERV=sapgw00 ERROR partner 'x.x.x.x:sapgw00' not reached TIME Sun May 5 10:15:14 201 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -10 MODULE nibuf.cpp LINE 4607 DETAIL NiBufIConnect: connection pending after 60000ms SYSTEM CALL connect ERRNO 55 ERRNO TEXT A connect operation on a socket is not complete. COUNTER 107 |
| 05.05.13 09:14:13 | Verarbeitungsfehler verursacht durch: com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Sun May 05 09:14:13 CEST 2013. This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds. Could not start server: Connect to SAP gateway failed Connection parameters: TPNAME=SAPXI_PRA GWHOST=x.x.x.x GWSERV=sapgw00 ERROR partner 'x.x.x.x:sapgw00' not reached TIME Sun May 5 09:14:13 201 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -10 MODULE nixxi.cpp LINE 2833 DETAIL NiPConnect2 SYSTEM CALL connect ERRNO 79 ERRNO TEXT A remote host refused an attempted connect operation. COUNTER 49 |
| 05.05.13 08:40:03 | Verarbeitungsfehler verursacht durch: com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Sun May 05 08:40:03 CEST 2013. This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 2048 seconds. Could not start server: Connect to SAP gateway failed Connection parameters: TPNAME=SAPXI_PRA GWHOST=x.x.x.x GWSERV=sapgw00 ERROR partner 'x.x.x.x:sapgw00' not reached TIME Sun May 5 08:40:03 201 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -10 MODULE nixxi.cpp LINE 2833 DETAIL NiPConnect2 SYSTEM CALL connect ERRNO 79 ERRNO TEXT A remote host refused an attempted connect operation. COUNTER 48 |
| 05.05.13 08:22:57 | Verarbeitungsfehler verursacht durch: com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Sun May 05 08:22:57 CEST 2013. This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 1024 seconds. Could not start server: Connect to SAP gateway failed Connection parameters: TPNAME=SAPXI_PRA GWHOST=x.x.x.x GWSERV=sapgw00 ERROR partner 'x.x.x.x:sapgw00' not reached TIME Sun May 5 08:22:57 201 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -10 MODULE nixxi.cpp LINE 2833 DETAIL NiPConnect2 SYSTEM CALL connect ERRNO 79 ERRNO TEXT A remote host refused an attempted connect operation. COUNTER 47 |
| 05.05.13 08:14:25 | Verarbeitungsfehler verursacht durch: com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Sun May 05 08:14:25 CEST 2013. This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 512 seconds. Could not start server: Connect to SAP gateway failed Connection parameters: TPNAME=SAPXI_PRA GWHOST=x.x.x.x GWSERV=sapgw00 ERROR partner 'x.x.x.x:sapgw00' not reached TIME Sun May 5 08:14:25 201 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -10 MODULE nixxi.cpp LINE 2833 DETAIL NiPConnect2 SYSTEM CALL connect ERRNO 79 ERRNO TEXT A remote host refused an attempted connect operation. COUNTER 46 |
* I replaced the ip of our gateway host with x.x.x.x
As you can see, PI tries to reconnect, first within a short time frame of 512 seconds (last line), then with 1024 seconds, 2048 seconds and then every 3600 seconds. As our sender SAP system was down a long time, at some point, SAP PI stopped trying (last try was 20130505 15:15:18).
At this point, as soon as the sending SAP system will come available again, the scenario is broken and will not work as communication channel is in erroneous status.
Q1: I know I can fix this by stopping and starting the communication channel when sending SAP system is up, but is there any way to make this more robust like automatically registering on startup of the sender system?
Q2: If not, I probably could specify a longer retry period / higher retry count. How / where would I have to specify this?
Thanks and kind regards
Jens