Solution : https://service.sap.com/sap/support/notes/99284 (SAP Service marketplace login required)
Summary :
When utilizing asynchronous Remote Function Calls (RFCs), the RESOURCE_FAILURE exception may trigger due to insufficient resources. This condition emerges predominantly when RFC groups lack necessary resources. To manage resource allocation for asynchronous RFCs, several SAP profile parameters need configuration, such as rdisp/rfc_min_wait_dia_wp for dialog work processes, rdisp/rfc_max_own_used_wp for user-related dialog work processes, rdisp/rfc_max_queue for dialog queue requests, rdisp/rfc_max_login and rdisp/rfc_max_own_login for system logons, and rdbp/rfc_max_comm_entries for communication entries. Proper adjustment of these parameters ensures optimal performance and avoids RESOURCE_FAILURE exceptions. For detailed parameter adjustment, functions such as TH_ARFC_GET_QUOTAS, TH_ARFC_SET_QUOTAS, and TH_ARFC_LOCAL_RESOURCES are recommendable. Adjustments should be done carefully to prevent system overload.
Key words :
user-related dialog work processes, profile parameter rdisp/rfc_min_wait_dia_wp, profile parameter rdisp/rfc_max_own_used_wp, profile parameter rdisp/wp_no_dia, profile parameter rdisp/rfc_max_queue, profile parameter rdisp/elem_per_queue, profile parameter rdisp/rfc_max_login, profile parameter rdisp/tm_max_no, profile parameter rdisp/rfc_max_own_login, profile parameter rdisp/rfc_max_comm_entries
Related Notes :
| 828725 | Parallel processing for flat file upload |
| 541311 | CC-INFO: Parallel processes FAQ |
| 212727 | CC-INFO: FAQs for parallel processes up to Release 4.6D |
| 194389 | Collective processing of production orders in background |
| 167626 | CIP2: Deactivation of parallel processing |