Solution : https://service.sap.com/sap/support/notes/726148 (SAP Service marketplace login required)
Summary :
In a SAP environment, instances of SAPLARFC are occupying several dialog work processes and gradually extending processing times without further CPU engagement or noticeable activity changes. The root issue stems from improper handling of transaction SMQ2 tRFC instances, resulting in lost rollability. Key parameters include 'rdisp/rfc_check' and 'rdisp/rfc_min_wait_dia_wp', requiring adjustment as per Note 74141 guidelines. Solutions involve process cancellation via SM50 and configuring dialog instances with adjusted parameters to manage dialog work processes effectively, avoiding RFC cascades and system blockages.
Key words :
abap statement 'set update task local', 'set update task local', processing time grows continuously, increase rdisp/rfc_min_wait_dia_wp proportionally, 000 gw/max_overflow_usage = 80 gw/req_stack_size = 150, rdisp/rfc_min_wait_dia_wp parameter set, application sends mass data, original rfcs continue processing, rdisp/rfc_check parameter set, rfcs send large datasets
Related Notes :
| 1423066 | Optimization of the performance in EWM |
| 1260137 | Work process status "Stopped RFC" by SAPLARFC (tRFC/qRFC) |
| 1250813 | SAPLARFC uses all dialog work processes |
| 888279 | Regulating/distributing the workflow load |
| 790672 | Processes terminate with TIMEOUT 'ARFC_END_TRANSACTION' |
| 565527 | Deadlock when using local update (IDocs) |