wasp on secondary hub takes over 45 minutes to start up

Products

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

Issue/Introduction

For some reason after upgrading from 20.3 to UIM v20.4 despite having the identical wasp.cfg that the Primary contains, it takes a long time to startup, over 40 minutes. The Secondary OC wasp is in a different AWS region than the database. The database and the primary hub and OC are in the same aws region.

Sep 22 16:22:00:843 DEBUG [main, com.nimsoft.nimbus.lookup.DataEngineLookup] Resulting parsed connection data is: DatabaseConnectionInfo [databaseName=<UIM_DB>, databaseServer=<database_server_name>, dbProvider=Oracle, nisJdbcUsername=<username>, nisJdbcPassword={not_shown_for_security_reasons}, nisJdbcUrl=jdbc:oracle:thin:@<FQDN>:1521/<db_instance_name>]

Sep 22 16:22:00:968 INFO  [main, com.nimsoft.nimbus.probe.service.wasp.Probe] jdbc/nis driver class name: oracle.jdbc.driver.OracleDriver Url: jdbc:oracle:thin:@<FQDN>:1521/<db_instance_name>] hibernate dialect: org.hibernate.dialect.Oracle9Dialect

reportscheduler.log

2023-10-09 12:02:52.457 [Catalina-utility-1]  ERROR com.broadcom.reportscheduler.ReportSchedulerServlet:init:28 reportscheduler.ReportSchedulerServlet - Error Initializing ReportSchedulerServlet 
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'resourceHandlerMapping' defined in class path resource [org/springframework/web/servlet/config/annotation/DelegatingWebMvcConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.web.servlet.HandlerMapping]: Factory method 'resourceHandlerMapping' threw exception; nested exception is java.lang.IllegalStateException: No ServletContext set
...
...
Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.web.servlet.HandlerMapping]: Factory method 'resourceHandlerMapping' threw exception; nested exception is java.lang.IllegalStateException: No ServletContext set

reportscheduler-1.log

2023-09-28 10:10:15.850 [scheduler_Worker-6]  ERROR com.broadcom.reportscheduler.service.JobManagerImpl:runAction:463 service.JobManagerImpl - Action failed: com.broadcom.reportscheduler.model.EmailAction@705a381[id=582,started=true,success=false,startTime=Thu Sep 28 10:10:15 EDT 2023,endTime=<null>,length=<null>,errorMessage=<null>,emailInfo=com.broadcom.reportscheduler.model.EmailInfo@5a7fb710[id=588,recipient=<email_address>,subject=<report_name>Daily Report,message=Attached is the daily <report_name> Daily Report]]
java.lang.NullPointerException: null
    at javax.mail.internet.InternetAddress.parse(InternetAddress.java:793) ~[javax.mail-1.6.2.jar:1.6.2]
    at javax.mail.internet.InternetAddress.parse(InternetAddress.java:752) ~[javax.mail-1.6.2.jar:1.6.2]
    at javax.mail.internet.InternetAddress.<init>(InternetAddress.java:119) ~[javax.mail-1.6.2.jar:1.6.2]
    at com.broadcom.reportscheduler.model.EmailAction.execute(EmailAction.java:82) ~[reportscheduler-api-20.4.9.jar:20.4.9]
    at com.broadcom.reportscheduler.service.JobManagerImpl.runAction(JobManagerImpl.java:452) [reportscheduler-api-20.4.9.jar:20.4.9]
    at com.broadcom.reportscheduler.service.JobManagerImpl.run(JobManagerImpl.java:349) [reportscheduler-api-20.4.9.jar:20.4.9]
    at com.broadcom.reportscheduler.quartz.ReportSchedulerJobRunner.execute(ReportSchedulerJobRunner.java:42) [reportscheduler-api-20.4.9.jar:20.4.9]
    at org.quartz.core.JobRunShell.run(JobRunShell.java:202) [quartz-2.3.2.jar:?]
    at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573) [quartz-2.3.2.jar:?]

Environment

• UIM 20.4 CU8
• Oracle database

Cause

• wasp report scheduler dialect initialization

Resolution

Deployed uim_reportscheduler-20.4.9-20231220.060356-40.zip to the secondary wasp.

Package is attached to this case.

wasp started up within 5 minutes.

We also checked the wasp.log and there were no errors.