Memory Leak Issue on APP or BG System Log

Products

• Clarity PPM On Premise

Issue/Introduction

Based on the error message in the app-server logs :
2021/04/08 22:35:03.826 | WARNING: The web application [niku] appears to have started a thread named [ProcessEngineMonitor] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread

Environment

Release : 15.7.1

Component : CA PPM INTEGRATIONS & INSTALLATIONS

Resolution

If there is no evidence of an out of memory issue, prepare for the event.

Perform the following steps:

### add the following JVM parameters to the APP and BG services

1. Make a copy of the current CLARITY_HOME\config\properties.xml files on all servers

2. For the Application (app) service:

a. Go to the CSA http://<server>:8090 > Application page

To set the updated JVM min and max size and to enable GC (garbage collection),
in the JVM parameter field, APPEND the field to be:

-XX:-UseGCOverheadLimit -XX:+HeapDumpOnOutOfMemoryError XX:HeapDumpPath=CLARITY_HOME\heapdump\clarity_oom_heap_dmp_serverX.hprof

NOTE: Be sure to replace the CLARITY_HOME with the correct install folder.

Do this for each APP server.

b. For the Background (bg) service:

Go to the CSA http://<server>:8090 > Background page

To set the updated JVM min and max size and to enable GC (garbage collection),
in the JVM parameter field, APPEND the field to be:

-XX:-UseGCOverheadLimit -XX:+HeapDumpOnOutOfMemoryError XX:HeapDumpPath=CLARITY_HOME\heapdump\clarity_oom_heap_dmp_serverX.hprof

NOTE: Be sure to replace the CLARITY_HOME with the correct install folder.

Do this for each BG server.

b. Restart all APP and BG services.

3. Wait until the issue reproduces. If so, check if the HPROF file gets reproduced.