Applying a patch wipes the Tomcat path from properties.xml
search cancel

Applying a patch wipes the Tomcat path from properties.xml

book

Article ID: 413370

calendar_today

Updated On:

Products

Clarity PPM On Premise

Issue/Introduction

Clarity services do not start up after installing 16.3.3 Patch 1 as the Tomcat directory has been wiped out on the propertes.xml file
Looking at the install.log file, we see the upgrade completed successfully.

Uploaded properties.xml
Trying to override old definition of task java

init:

postupgrade:
Installation Successful - 02-October-2025 09:55:33
Trying to override old definition of task java

_postprocess-upgrade:

BUILD SUCCESSFUL

However at the time the service start all command is executed, we see the following warnings:

Deploying service(s)...
WARNING: This service requires Apache Tomcat version 8 or higher
/opt/clarity/.setup/scripts/deploy.xml:177: The following error occurred while executing this line:
/opt/clarity/.setup/scripts/
Failure occured:
deploy.xml:192: The following error occurred while executing this line:
/opt/clarity/.setup/scripts/j2ee/tomcat/deploy.xml:68: T/opt/clarity/.setup/scripts/deploy.xml:176: /opt/clarity/.setup/scripts/deploy.xml:177: The following error occurred while execuhe following error occurred while executing this line:
/opt/clarity/.setup/scripts/j2ee/tomcat/deploy.xml:1003: src '/lib/cataliting this line:
/opt/clarity/.setup/scripts/deploy.xml:192: The following error occurred while executing this line:
/opt/clarityna.jar' doesn't exist.
        at org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:582)
        at org.apache/.setup/scripts/j2ee/tomcat/deploy.xml:68: The following error occurred while executing this line:
/opt/clarity/.setup/scripts/j.tools.ant.taskdefs.Ant.execute(Ant.java:440)
        at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:106)
        at com.2ee/tomcat/deploy.xml:1003: src '/lib/catalina.jar' doesn't exist.

Cause

The Tomcat directory has been wiped out on the propertes.xml file

Resolution

In order to resolve this issue:

  • Edit the Properties.xml file
  • Look at the Tomcat home directory and ensure this is updated to point to the current directory