The probeDiscovery queue is queuing up with these messages in the discovery_server log file: Waiting to obtain UDM database connection properties: (11) command not found

Document ID : KB000008005
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

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... 

 

Environment:
Windows or LinuxUIM 8.51discovery_server 8.51udm_manager 8.51
Cause:

The 'out of the box' memory settings for the udm_manager are not enough in busy environments:

<opt> 

java_mem_init = -Xms96m 

java_mem_max = -Xmx1024m 

java_opts = -server -XX:ErrorFile=./hs_err_pid.log -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode 

</opt> 

 

Resolution:

Using Raw Configure (enter "Infrastructure Management" Console and CTRL-Right click udm_manager)

to modify the setting "java_mem_max" to a higher value such as 4 GB: java_mem_max = -Xmx4096m