wasp startup failed after upgrade to UIM 23.4 CU6 and was green, had pid but no port

Products

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

Issue/Introduction

After upgrading DX UIM 23.4 from CU4 to CU6, the wasp probe would not start.

wasp.log

Caused by: org.apache.catalina.LifecycleException: A child container failed during start
at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:733)
at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:767)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:164)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1162)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1158)
at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:57)
at java.base/java.lang.Thread.run(Unknown Source)
Caused by: java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[wasp-engine].StandardHost[localhost].StandardContext[/mps]]

Environment

• DX UIM 23.4 CU6
• wasp 23.4.6

Cause

• leftover webapp artifacts, some not upgraded for previous UIM CU version

Resolution

wasp startup failed after upgrade to CU6 and was green and had a pid but no port. The PID kept changing.

First, deleted any extraneous/unnecessary webapps sections as the wasp threw only a cabi webapp error and then some other generic webapp failures:

1. cabi
2. samlsso (normally not required for deletion but not used in this environment)
3. webservices

Second, upgraded:

1. mcsuiapp_portlet from 23.4.4 to 23.4.6 which did not happen during the upgrade
2. mps from 23.4.4 to 23.4.6 which did not happen during the upgrade

Third,  for the sake of MCS performance, adjusted mon_config_service startup options from 512/1024 MB to its previous setting of 2048/4096 MB. These java startup options and string were overwritten during the upgrade.

wasp then started up successfully.