(DI-2305) No aRFC resources available for application server
When no aRFC resources are available for the specific application server, you will receive a message “No ARFC resources were available after &1 seconds on server &2” and KPIs might be not collected for this specific server. This message means that the collector job tries to find a free aRFC resource for a specific server, but there was none available in N-seconds.
There might be two scenarios when no aRFC resources are available:
On a central server on which the collector job is executed
The Collector job can not be executed on this server as it has no aRFC resources available and no KPIs are collected
On a remote server for which the collector job tries to collect KPIs on the remote system from the central system
This server is excluded from monitoring and the Collector job will collect data from all available application servers except this specific server with no aRFC resources
In case you would like to check the aRFC resources on the specific server, please check the transaction SARFC. Additionally, you might check all running WPs on a specific server in transaction SM50. Please make sure that you are executing these transactions on the specific application server:
If it is a central server, execute transactions on the central system and relevant application server.
If it is a remote server, execute transactions on the remote system and relevant application server.
Also please be aware that if no aRFC resources are still available for a specific application server, you might have a problem to login into this server during your investigation. In such a case, check with your basis team why all these aRFC resources are consumed and which WPs are running on this application server.
Configuration of Maximum waiting time for free aRFC resources on Central server
Each collector job is checking for free aRFC resources on the central server, on which is this background job executed. By default, it checks for 10 secs. If no aRFC resources are found after 10 seconds, the collector job is not executed and no data is collected. You might adjust this maximum waiting time threshold in Configuration properties.
Go to the transaction /DVD/MON_SYS
Go to the node Configuration
Find the property name MAX_WAIT_FOR_FREE_ARFC_RES
Change the value from 10 seconds to a custom value
Save the changes
Configuration property for Maximum waiting time to check available aRFC resources (in seconds)
Additionally, if you are experiencing this issue quite often for one server, you might define a custom Job Server Group in transaction SM61. You might then assign created custom Job Server Group into configuration property BTC_SERVER_GROUP. When collector jobs restart, these jobs will be executed only on server(s) specified in this custom Job Server Group.
Configuration of Maximum waiting time for free aRFC resources on Remote server
Collector job is checking the availability of each application server for the remote system. By default, it checks the aRFC resources for 10 seconds for each application server. If no aRFC resources are found after 10 seconds, the specific application server is marked as not reachable and this server is excluded from monitoring. The reason for this exclusion is that if this server will be monitored, the collector job might be waiting for free aRFC resources for a long time and hanging on the system. For other available application servers, the data will be collected correctly.
You might adjust the default maximum waiting time for free aRFC resources for remote servers in System parameters for the specific remote systems:
Go to the transaction /DVD/MON_SYS
Select the remote system
Go to the sub-node System parameters in the System maintenance
Create a new system parameter (F5)
Set the parameter name MAX_WAIT_TIME_FOR_ARFC and provide a custom waiting time in seconds.
Save the changes
System parameter to define custom value for maximum waiting time for free aRFC resources for remote server