wasp probe fails to start after UMP update to 9.2.2

book

Article ID: 192953

calendar_today

Updated On:

Products

NIMSOFT PROBES DX Infrastructure Management

Issue/Introduction

ISSUE:
UMP Wasp probe fails to start after UMP update to 9.2.2 for SAML compatibility 


WASP LOG:
May 14 20:17:59:347 ERROR [wasp-engine-startStop-1, org.apache.catalina.core.ContainerBase] startInternal() A child container failed during start
May 14 20:17:59:350 ERROR [wasp-engine-startStop-1, org.apache.catalina.core.ContainerBase] java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[wasp-engine].StandardHost[localhost].StandardContext[/DashboardAPI]]
 at java.util.concurrent.FutureTask.report(FutureTask.java:122)

PORTAL.LOG
Caused by: org.dom4j.DocumentException: Error on line 44 of document  : cvc-complex-type.2.4.a: Invalid content was found starting with element 'active'. One of '{"http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd":security-role-ref, "http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd":supported-processing-event, "http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd":supported-publishing-event, "http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd":supported-public-render-parameter, "http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd":container-runtime-option}' is expected. Nested exception: cvc-complex-type.2.4.a: Invalid content was found starting with element 'active'. One of '{"http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd":security-role-ref, "http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd":supported-processing-event, "http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd":supported-publishing-event, "http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd":supported-public-render-parameter, "http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd":container-runtime-option}' is expected.
 at org.dom4j.io.SAXReader.read(SAXReader.java:482)
 at org.dom4j.io.SAXReader.read(SAXReader.java:365)
 at com.liferay.portal.xml.SAXReaderImpl.read(SAXReaderImpl.java:425)
 ... 33 more

Cause

Bad wasp configuration, unexpected entries in the wasp.cfg

What caused the wasp not to start for this customer were entries like:

  <dapi>, <umpjslib> and <umpmedia> 

Environment

Release : UIM 9.2 / UMP 9.2.2

Component : wasp 9.2.2

UMP: CentOS 7
UIM: CentOS 7
MySQL 5.6.20

Resolution

1) Deactivate wasp probe

2) Open wasp.cfg file, which is available in /opt/nimsoft/probes/service/wasp directory

3) Find and delete the following three blocks (dapi, umpjslib, umpmedia) from wasp.cfg

 

  <dapi>
        reloadable = true
        <log>
            <com.nimsoft.ws.dashboardapi>
                loglevel = 3
            </com.nimsoft.ws.dashboardapi>
        </log>
        load_on_startup = true
        allow_cleartext_passwords = false
        path = /DashboardAPI
    </dapi>

 

    <umpjslib>
        reloadable = true
        cross_context = true
        load_on_startup = true
        unpack_war = true
        path = /umpjslib
    </umpjslib> 

 

    <umpmedia>
        media_path = umpmedia/
        reloadable = true
        cross_context = true
        load_on_startup = true
        unpack_war = true
        path = /umpmedia
    </umpmedia>

 

4) Activate wasp probe / unexpected entries