In the "hub" status, the "probeDiscovery" queue is queueing up.
The discovery_server.log file is filled with the following errors:
20 Aug 2017 21:02:08,368 [main] WARN com.nimsoft.udm.utilities.nimbus.UdmConnectionLookup
- Waiting to obtain UDM database connection properties: (11) command not found,
Received status (11) on response (for sendRcv) for cmd = 'getUdmDatabaseConnection' Retrying...
Windows or Linux
The 'out of the box' memory settings for the udm_manager are not enough in busy environments:
java_mem_init = -Xms96m
java_mem_max = -Xmx1024m
java_opts = -server -XX:ErrorFile=./hs_err_pid.log -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode
1 - Using Raw Configure (enter "Infrastructure Management" Console and CTRL-Right click udm_manager probe)
2 - modify the setting "java_mem_max" to a higher value such as 4 GB
java_mem_max = -Xmx4096m