The OC wasp probe takes hours to start after upgrading DX UIM 23.4 from CU3 to CU5

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

After upgrading DX UIM 23.4 from CU3 to CU5, the wasp probe on the OC robot takes several hours to start.

In this scenario, CABI is installed on the OC robot.

Error captured in the X..:\Nimsoft\probes\service\wasp\logs\reportscheduler.log

[Catalina-utility-1]  WARN  org.springframework.context.support.AbstractApplicationContext:refresh:635 support.ClassPathXmlApplicationContext - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'quartzSchedulerImpl' defined in class path resource [spring/application-config.xml]: Cannot resolve reference to bean 'jobManager' while setting constructor argument
[Catalina-utility-1]  ERROR com.broadcom.reportscheduler.ReportSchedulerServlet:init:33 reportscheduler.ReportSchedulerServlet - Error Initializing ReportSchedulerServlet 
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'quartzSchedulerImpl' defined in class path resource [spring/application-config.xml]: Cannot resolve reference to bean 'jobManager' while setting constructor argument

Resolution

This issue occurs because CABI is installed on the OC robot, which is not supported with UIM version 23.4.5 and above. To resolve this, CABI must be uninstalled from the OC robot.

 

Refer to the article titled Uninstall cabi in DX UIM 23.4x - cabi cleanup process for detailed instructions on the cabi removal and cleanup procedure.

Additional Information

Install or Upgrade for a Bundled CABI Server