This document describes how to add Java Virtual Machine (JVM) flags to the JAVA_OPTS in the CloudCenter Manager (CCM).
Cisco recommends that you have knowledge of these topics:
Virtual Machine Environment
The information in this document is based on these software versions:
CloudCenter version 4.x
At times, the TOMCAT process goes unresponsive and stops to function properly but there is no information that indicates the reason why the TOMCAT went unresponsive.
Users are unable to log into CloudCenter and users who are logged in to the CloudCenter see the CCM User Interface (UI) unresponsive. This issue can be triggered because the TOMCAT service does not run and it has stopped to work. Then, the CCM default logs do not show any details or the reason as to why the TOMCAT service has stopped to work.
In order to collect additional information before the TOMCAT service stops to run, JVM flags need to be added to the JAVA_OPTS which is in the /usr/local/tomcat/bin/setenv.sh. These parameter helps you to collect the heap dumb of the JAVA process and the Garbage Collection statistics of the JAVA process. Then, when the TOMCAT process becomes unresponsive, it generates /usr/local/tomcat/logs/ccm.bin and /usr/local/tomcat/logs/ccm-gc.log.
Step 1. Add these parameters at the /usr/local/tomcat/bin/setenv.sh.