Tomcat Log Analysis Job Fails

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

Tomcat Log Analysis Job fails with error "Exiting abnormally with error: Connection refused to host".

This situation happens when the application services are restarted within the cluster without restarting the BG services, even though admin list clients commands run from any of app servers list out the correct app servers

Steps to Reproduce:

1. Run the Tomcat Log Analysis Job.

Expected Results: Tomcat Log Analysis Job should be successful.

Actual Results: Tomcat Log Analysis Job fails with error " Exiting abnormally with error: Connection refused to host". Below errors can be seen in the admin log.

09-SEP-24 12.03.43 PROCESSING "Exiting abnormally with error: Connection refused to host: XX.XX.XX.XX; nested exception is:
java.net.ConnectException: Connection timed out"
08-SEP-24 12.03.43 PROCESSING "Exiting abnormally with error: Connection refused to host: XX.XX.XX.XX; nested exception is:
java.net.ConnectException: Connection timed out"
07-SEP-24 12.03.43 PROCESSING "Exiting abnormally with error: Connection refused to host: XX.XX.XX.XX; nested exception is:
java.net.ConnectException: Connection timed out"
06-SEP-24 12.03.43 PROCESSING "Exiting abnormally with error: Connection refused to host: XX.XX.XX.XX; nested exception is:
java.net.ConnectException: Connection timed out"
05-SEP-24 12.03.43 PROCESSING "Exiting abnormally with error: Connection refused to host: XX.XX.XX.XX; nested exception is:
java.net.ConnectException: Connection timed out"

Environment

Clarity 16.1.x, 16.2.x, 16.3.0

Cause

DE154541

Resolution

This issue is fixed in:

• Clarity 16.3.1
• Clarity 16.3.0 Patch 1 (16.3.0.1)
• Clarity 16.2.3 Patch 2 (16.2.3.2)

Workaround:

• Restart all the clarity services, then run Tomcat Log analysis job.