Tomcat Service in Stopped State Post Upgrade — Older Java Version Referenced

Products

• VMware Smart Assurance

Issue/Introduction

Post MnR upgrade, the Tomcat service is found in a stopped state. The Tomcat process is referencing the Java version from the previous MnR installation.

Environment

All supported Watch4net|M&R version upgrade in RHEL 9.x

Cause

The Tomcat process retains a reference to the older MnR Java version following the upgrade, causing the service to remain in a stopped state.

Resolution

• Verify the Tomcat service status.

• Confirm that the Tomcat process is referencing an older MnR Java version.       

    bin/manage-modules.sh service status all
        Checking 'topology-mapping-service Default'...[running ]
    Checking 'webservice-gateway Default'... [running J
    Checking 'collector-manager emc-watch4net-health'... [running l 
    Checking 'event-processing-manager emc-watch4net-health'….[running ] 
    Checking 'tomcat Default'... [ stopped ] 
    Checking 'task-scheduler Default'... [running ]

    ps -ef |grep -i tomcat
    apg 36941 1 0 15:22 ?  00:00:24 /opt/APG79upgrade/Tools/Update-Manager/7.9.0.1/data/Sun-JRE_8.0.461/bin/java -Dapg.resources.webapps.dir......

• Terminate the existing Tomcat process. (kill -9 36941 for the above example)

• Start the Tomcat service.

• Validate that the service is running and the MnR UI is accessible.