Write the amount of heap space memory used by vCenter Orchestrator every 10 seconds in the server.log file.

Copy the file in $INSTALL_DIR/app-server/server/vmo/deploy/ and restart your server.

Disclaimer : This is not part of the official vCO distribution and not supported by VMware. Use at your own risk.


What version of vRO does this apply to?  I have a customer using vRO 5.5 and they are having Java Heap issues and I'm wondering if I can recommend this to them.  Also, on your blog post from 5 years ago ( you mention that it is possible to visually monitor the Java heap with VisualVM.  Is this still a viable option?


In 5.5 and later the disk layout of the server has changed. The way to connect with jvisualvm or jconsole to vCO is given below. Then you add jmx connection to port 2838 in jvisualvm and connect to it. To browse jmx beans in jvisualvm you need to install additional plugin for this. you can use jconsole for this if you can not install the jmx plugin.

1.    Append the following to /usr/lib/vco/app-server/bin/ JAVA_OPTS="$JAVA_OPTS"

2.    Change the following in /etc/vco/app-server/ java.rmi.server.hostname=<vco ip address>

3.    Restart vco-server service.

Note!! This will expose port 2838 on the public interface and will allow unauthorized access to vco server process. Make sure that the network segment that can access vco is secured or take other measures to restrict it.

Version history
Revision #:
1 of 1
Last update:
‎09-19-2011 03:15 AM
Updated by: