Fixing “Timeout is over” When InboundRA Fails to Start in SAP PI/PO
When you restart your SAP Process Integration / Process Orchestration system, you may notice that the InboundRA resource adapter does not come up. In the default trace you’ll typically see a deployment error for inboundRA and a runtime exception indicating that the timeout is over and the RA is blocking during startup.
This behavior is usually not a coding bug, but a startup timeout issue: the InboundRA initialization takes longer than the default allowed time, so the Java engine aborts its startup.
Solution
SAP’s recommendation in KBA 3248995 – “InboundRA fails to start with the error Timeout is over” is to adjust the startup timeout of the resource adapter via the parameter RAStartupTimeout.
This can be done from:
- Start configtool (Windows configtool.bat, Unix/Linux configtool.sh) from folder /usr/sap/<SID>/<inst_Nr>/j2ee/configtool.
- From View menu set Expert Mode flag.
- Navigate to Configtool -> cluster-data -> template -> services -> connector -> RAStartupTimeout
- Adjust the “RAStartupTimeout” property to the expected value in seconds.
The default timeout value is 480 seconds.