Solution : https://service.sap.com/sap/support/notes/103523 (SAP Service marketplace login required)
Summary :
This SAP Note addresses the issue where RFC load distribution via the SAP logon mechanism fails to occur. The primary cause identified is the insufficient refresh rate of the load distribution data among servers in a logon group, set by default to every 5 minutes, which doesn't support high-intensity, parallel processing demands. The solution proposed for applications requiring large-scale parallelization involves utilizing asynchronous RFC for load distribution rather than transactional RFC. Additionally, applications overwhelming the system are advised to implement tuning measures and potentially reconfigure the number of R/3 instances, with assistance from the Early Watch team.
Key words :
abap key word call function func starting, abap key word call function func, additional key words logon groups, rfc-internal load distribution procedure, profile parameter rdisp/autoabaptime, application executes tuning measures, remote function call, sap logon mechanism, massive parallel processing, check online documentation
Related Notes :
| 986373 | RFC load distribution |
| 593058 | New RFC load balancing procedure |
| 549981 | Determining system resources for parallel RFCs |
| 541311 | CC-INFO: Parallel processes FAQ |
| 212727 | CC-INFO: FAQs for parallel processes up to Release 4.6D |
| 95633 | tRFC: Problems with high load |
| 74141 | Resource Management for tRFC and aRFC |
| 16201 | Background program, timeout, SAPMSSY6 |