MCS profiles remain stuck in notified state in 23.4 CU4

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)
• CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)
• CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

DEBUG [attach_socket, com.ca.uim.probes.archive.ProbeDistributionService] ProbeDistributionService.isProbeInstalled:247:    Probe is not installed.[MCS-902] Response from the probe_list callback indicates the the probe cdm is not installed on the robot <nimBUS_Address_of_robot>, MCS-902
Feb 27 10:40:28:886 INFO  [attach_socket, com.ca.uim.probe.mcs.readerService.secondary.SecondaryConfigPusherThread] [Step 2/8] Required probe missing on target robot. Attempting to deploy the probe on robot.
Profile: 4089752
Probe: cdm
Robot: <nimBUS_Address_of_robot>
Feb 27 10:40:28:887 DEBUG [attach_socket, com.ca.uim.probes.archive.ProbeDistributionService] ProbeDistributionService.isProbeInstalled:243:    Probe is not installed.(3) invalid argument, supplied address is not a valid UIM robot address
Feb 27 10:40:28:887 INFO  [attach_socket, com.ca.uim.probes.archive.ProbeDistributionService] ProbeDistributionService.getInstance:53:    Failed to fully initialize the probe distribution service. (90) Configuration error, Failed to find address of the automated distribution engine

Environment

• cdm 8.03
• DX UIM 23.4 CU4

Cause

• ADE java min/max too low

Resolution

ADE was failing to send the cdm 8.03 package to the robot. I had to increase the ADE memory from the defaults of 64m min and 512m max.

 

After increasing the java min/max memory to 1024/2048, the cdm package was successfully distributed and all three systems no longer have profiles stuck in 'notified' status.