WASP probe not starting after upgrade from 20.3 to 20.4 CU5
search cancel

WASP probe not starting after upgrade from 20.3 to 20.4 CU5

book

Article ID: 265085

calendar_today

Updated On:

Products

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

Issue/Introduction

We upgraded our DX UIM Dev environment from 20.3.0 to 20.45 but after upgrading our OC server WASP probe, we have an issue.

May 01 06:35:22:570 ERROR [Catalina-utility-1, org.apache.catalina.core.ContainerBase] startInternal() A child container failed during start
May 01 06:35:22:570 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@407f89b0]
    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:926)
    at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:835)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
    at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1396)
    at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1386)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
    at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.catalina.LifecycleException: Failed to start component [org.apache.catalina.webresources.StandardRoot@407f89b0]
    at org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBase.java:440)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:198)
    at org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:4886)
    at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5024)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
    at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1396)
    at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1386)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
    at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134)
    at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:919)
    ... 11 more
Caused by: java.lang.IllegalArgumentException: The main resource set specified [C:\Program Files (x86)\Nimsoft\probes\service\wasp\webapps\webservices_rest] is not valid
    at org.apache.catalina.webresources.StandardRoot.createMainResourceSet(StandardRoot.java:762)
    at org.apache.catalina.webresources.StandardRoot.startInternal(StandardRoot.java:719)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
    ... 20 more

Environment

  • Release: DX UIM 20.4 CU 5
  • Upgraded from 20.3.0 to 20.45
  • wasp v20.45
  • robot v9.36
  • webservices_rest 20.30

Cause

  • webservices_rest child container failed to start after upgrade to CU5

Resolution

Remove the webservices_rest package by following the steps below:

  1. Login to Admin Console 
  2. Navigate to the the robot
  3. Probes
  4. controller
  5. select 'View Probe Utility in New Window'
  6. select inst_pkg_remove
  7. enter the name->webservices_rest in either the 'probe' or 'package' field. 
  8. click the green arrow to delete it
  9. Deactivate wasp
  10. Activate wasp

The following section should then be gone from the wasp.cfg and the wasp should start up.

<webservices-rest>
        reloadable = true
        cross_context = true
        load_on_startup = true
        maintenance_mode_timeout = 30000
        unpack_war = true
        doc_base = webservices_rest
        path = /rest
    </webservices-rest>

If and when it does start up successfully and you can successfully login to the OC, you can readd the webservices_rest package (20.46) to the OC robot via drag and drop.

Download the atest GA version of webservices_rest, e.g., v23.4.3 from support.nimsoft.com

Powered by Wolken Software