Wasp fails to start and throws error a child container failed during start
search cancel

Wasp fails to start and throws error a child container failed during start

book

Article ID: 258605

calendar_today

Updated On:

Products

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

Issue/Introduction

wasp probe on OC robot does not start because it doesn't extract the webapps.

INFO  [Catalina-utility-1, org.apache.catalina.core.ContainerBase.[wasp-engine].[localhost].[/]] No Spring WebApplicationInitializer types detected on classpath Feb 24 17:18:44:050
ERROR [Catalina-utility-1, org.apache.catalina.core.ContainerBase] startInternal() A child container failed during start 
ERROR [Catalina-utility-1, org.apache.catalina.core.ContainerBase] java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [org.apache.catalina.webresources.StandardRoot@173e0d4f]     
at java.util.concurrent.FutureTask.report(FutureTask.java:122)     
at java.util.concurrent.FutureTask.get(FutureTask.java:192)     
at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:916)     
at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:841)     
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)     
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1384)     
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1374)

and/or

Caused by: java.lang.IllegalArgumentException: The main resource set specified [D:\UIM\probes\service\wasp\webapps\cabi] is not valid
             at org.apache.catalina.webresources.StandardRoot.createMainResourceSet(StandardRoot.java:751)
             at org.apache.catalina.webresources.StandardRoot.startInternal(StandardRoot.java:708)
             at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)

Environment

  • UIM 20.3 or 20.4
  • Windows OS

Resolution

  1. Open registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NimbusWatcherService.
  2. In the key "ImagePath" change the value to path (using the same case) as it appears in Windows Explorer. (for e.g. "C:\Program Files\Nimsoft\bin\nimbus.exe"). **
  3. Restart the "Nimsoft Robot Watcher" service

 

**: ensure the paths are exactly the same, maintaining upper or lower case as even an upper case vs lower case can cause this issue.