Solution : https://service.sap.com/sap/support/notes/1250813 (SAP Service marketplace login required)
Summary :
SAP Note addresses a TIME_OUT ABAP runtime error caused by program SAPLARFC when handling dialog work processes. The error stems from a specific RFC cascade issue and occurs if SET UPDATE TASK LOCAL is used with t/qRFC requests in updates, leading to deadlock and rollability loss post-COMMIT WORK. Solutions include registering RFC destination NONE in SMQS with appropriate connection settings and dynamically setting rdisp/rfc_check to "2" in RZ11. For systems heavily using qRFC, a dedicated server is recommended. Implementing these measures and closing 20% of blocked DIA processes can resolve the issue without needing a restart.
Key words :
abap statement set update task local, abap runtime error time_out occurs, abap runtime error time_out, parameter rdisp/rfc_check dynamically, abap runtime error, user context loses, local update reason, blocked dia processes, standalone program dpmon, dialog work processes
Related Notes :
| 1403974 | Determining the maximum connections in transaction SMQS |
| 1260137 | Work process status "Stopped RFC" by SAPLARFC (tRFC/qRFC) |
| 925855 | "Stopped CPIC" when you use tRFC or qRFC and local update |
| 726148 | SAPLARFC occupies all work processes, RFC cascade |
| 74141 | Resource Management for tRFC and aRFC |