search cancel

Wasp probe takes too much time to start, after upgrading UIM to 9.1.0 version.

book

Article ID: 134393

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Even after excuting the procedure of the KB (https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=132483), the Wasp probe total startup time is still bigger comparing to the 9.02 version.

Cause

This happens due to the tomcat 9 behavior of class path and manifest scanning. 

Environment

Release : 9.1.0

Component : UNIFIED INFRASTRUCTURE MGMT

Resolution

Please execute the procedure below in UMP machine:


1- Deactivate wasp probe;

2- On the UMP robot machine navigate to "...\probes\service\wasp\conf" directory;

3- Open the "context.xml" for editing;

4- Replace the "context.xml" file contents with the following text:

  

 <?xml version='1.0' encoding='utf-8'?>

  <Context reloadable="false">

    <!-- Disable session persistence across restarts. -->

    <Manager pathname="" />

    <Resources cachingAllowed="false" />

    <JarScanner scanClassPath="false" scanManifest="false" >

      <JarScanFilter pluggabilitySkip="*.jar" defaultPluggabilityScan="false" tldSkip="*.jar" defaultTldScan="false"/>

    </JarScanner>

  </Context>


5- Activate Wasp probe;