This document describes how to use Java Console (jconsole) tool to troubleshoot Cisco Unified Customer Voice Portal (CVP) memory leak issues.
Cisco recommends that you have knowledge of these topics
Cisco Unified Customer Voice Portal (CVP)
Java Console utility
The information in this document is based on CVP version 9.0(X) and above.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
To troubleshoot Call Server, VXML server memory leak or performance related issues often it is necessary to turn up java heap dump trace in jconsole utility. This is usually done after you have narrowed down a resource problem to a specific service or services in the server via event viewer, task Manager, and/or perfmon logs tools. The utilities dump heap is a low level trace file and is recommended to be turned up on top of CVP troubleshoot trace level.
Jconsole by default is located in the path C:\Cisco\CVP\jre\bin of Call Server, VXML, and OAMP servers and to log in to the console you must first configure the port details in jmx_callserver.conf, jmx_vxml.conf, and jmx_oamp.conf configuration files of these servers respectively:
Call Server JMX port 2098
VXML Server JMX port 9696
OAMP server JMX port 10001
After the configuration file is updated, run the utility jconsole as explained in these steps:
Step1. Open %CVP_HOME%/CVP/jre/bin/jconsole.exe.
Step2. Connect to localhost, and specify the port number corresponding to Callserver, VXML or OAMP server JMX port.
Step3. Log in with CVP oamp or Admin credentials.
Step4. Open MBeans tab.
Step5. Open com.sun.management - HotSpotDiagnostics - Operations - dumpheap.
Step6. In p0 enter a file name and path to which you want to direct the dump. Leave p1 as true. Click on dumpHeap button and collect the generated file.
Note: This tool is intended to troubleshoot VXML server memory leak issues. Once the application which causes the leak is identified, this tool must be enabled, desired information must be gathered and after the problme is recreated, it must be disabled. Jconsole is not designed as a monitor tool and must not be enabled indefinitely.