Host Connection By SNMP job is failing with below error:
<message>[CDATA: maximum number of DatagramSockets reached]</message>
Such error is coming out of the limiation with the JVM.
The error message is reporting that the probe Java virtual machine (JVM) has used all available datagram sockets. Process is running out of UD Datagram sockets and hence one see this error.
It usually happens when Host Connection By SNMP runs against large number of trigger CIs and got into hung state and sockets don't get released.
As a result, it is suggested to increase the limitation and restart the JVM related to probe.
Workaround / Fix
Increase the UDP socket limitation for the JVM.
As follow are the changes which can be implement and rerun the job.
#1, Add the following line to WrapperManagerCustom.conf and WrapperGateway.conf configuration files on the probe. wrapper.java.additional.24=-Dsun.net.maxDatagramSockets=90
At the same time, it is advisable to increase the below setting also along with the above setting.
#2, In the DataFlowProbe.properties file on the discovery probe, change values as follows: appilog.agent.local.services.defaultMaxJobThreads = 90 appilog.agent.local.services.adHocMaxThreads = 45
change only for the specific adapter like Host Conection by SNMP like below.
#3, In the “Host Connection by IP” and “Host Connection by SNMP” discovery patterns change the number of threads to 45.
This is applicable to all the versions of UD.