Solution : https://service.sap.com/sap/support/notes/948636 (SAP Service marketplace login required)
Summary :
When attempting to start an external program on a local application server, a timeout error occurs that does not align with the gw/cpic_timeout setting of 20 seconds but instead manifests after 62 seconds. This discrepancy appears in Gateway Trace and errors indicating the conversation ID could not be found after the initiate sequence executed by fork() and exec(). A typical work process confirms a successful start only after 62 seconds, which leads to a detection issue and subsequent termination by the SAP Gateway due to a cpic_timeout conflict. To resolve this, ensure use of rfc/use_gwstart=1 per SAP Note 638701 to correct communication initiation from the RFC layer.
Key words :
11 2006 release 640 component sap gateway version 2 rc 242 module gwr3cpic, 11 2006 release 640 component sap gateway version 2 rc 728 module gwxxrd, choosing goto -> trace -> external programs, host xxser1 / sapgw00 error timeout, host sapbc1 / sapgw00 error conversation 27005309, allocate time wed mar 15 09, allocate fork exec fork, found time wed mar 15 09, work process successfully obtains, line 5778 counter 596 error => gwiconnect
Related Notes :
| 1371799 | Starting tp via gateway is not allowed |
| 638701 | Starting RFC servers takes too long |