uCMDB version: 9.05.CUP12.351
DDM Content Pack 11.08.802
This is a generic question about probes and their capabilities.
While running heavy jobs like Host Networking by SNMP or VLAN related jobs, I check the probe jmx (Local_probeFQDN --> type=JobsInformation -->Description of viewJobsStatuses), for stuck threads, run duration, etc. Often, I see that all of the 8 threads(Default) are stuck and remain stuck for hours together.
When I play with the Discoveryprobe.properties file and change a few things like the Max Threads, Max Stuck threads, Time until the probe waits, after reaching a certain number of stuck threads, for a restart and other stuff, it doesn't seem to be helping us. I would love to know how to achieve an efficient and fast discovery process.
Also, is there a way to fix these stuck threads so that the job continues without interruptions, other than logging on to the probe box and bouncing them ?
Please share your thoughts.