IBM Tivoli Monitoring for Virtual Environments, Version 7.2 Fix Pack 3

Increasing the Java heap size

After you configure the VMware VI agent, if you are monitoring a large VMware environment, then you might need to increase the heap size for the Java™™ data provider.

The default heap size for the Java data provider is 256 megabytes. In large VMware environments, if the following problems arise, then you might need to increase the heap size:
  • The Java data provider stops because of a javacore problem, and creates a file that is named javacore.date.time.number.txt in the CANDLEHOME\tmaitm6_x64 directory.
  • The javacore.date.time.number.txt file contains the string java/lang/OutOfMemoryError.

Use the following heap size values according to the number of ESX servers that you want to monitor:

Table 1. VMware environment and Java heap size
VMware environment Java heap size
Small environment: A vCenter server that manages up to 125 ESX(i) servers and 300 to 1500 guests. 2 GB
Note: For a very small environment with a vCenter that manages 15 to 20 ESX(i) servers, use the default java heap size that is provided by the data provider.
Medium environment: A vCenter server that manages between 125 to 250 ESX(i) servers and 1500 to 4000 guests. 4 GB
Large environment: A vCenter server that manages between 250 to 500 ESX(i) servers and 4000 to 7500 guests. 8 GB
Very large environment: A vCenter server that manages more than 500 ESX(i) servers and more than 7500 guests. 16 GB
To increase the heap size for the Java data provider, complete the following steps:
  • On a Windows system:
    1. Open the file %CANDLE_HOME%\TMAITM6_x64\kvm_data_provider.bat.
    2. Add the following line before the line that starts with SET KVM_JVM_ARGS="$KVM_CUSTOM_JVM_ARGS...:
      SET KVM_CUSTOM_JVM_ARGS=-Xmx512m
    3. Restart the agent.
  • On a Linux system:
    1. Open the file $CANDLEHOME/platform/vm/bin/kvm_data_provider.sh.
    2. Add the following line before the line that starts with KVM_JVM_ARGS="$KVM_CUSTOM_JVM_ARGS...:
      KVM_CUSTOM_JVM_ARGS=-Xmx512m
    3. Restart the agent.


Feedback