Java Garbage Collector is consuming more memory and making ITPAM unresponsive

Products

• CA Process Automation Base

Issue/Introduction

Periodically (every 1-2 weeks) the system is fully busy by the Java Garbage Collector so that processes cannot be processed anymore, run into a timeout, and cannot be called from the GUI anymore. The problem can be "solved" by restarting the CA PAM services on both servers. Afterwards, the processes need to be restarted, and also CA Catalog needs to be restarted

Environment

CA PAM 04.3.05 on Windows

Resolution

Kindly increase Java memory as below:

For Catalog in the viewservice.conf update values as below:

wrapper.java.initmemory : 4096
wrapper.java.maxmemory : 6144

For ITPAM in the c2osvcw.conf update values as below in ITPAM 4.3 version:

wrapper.java.maxmemory=8192

In ITPAM 4.4 version update values as below:

wrapper.java.additional.4=-Xms4096M
wrapper.java.additional.5=-Xmx8192M

Restart both the services.