/var/log/cm-inventory/cm-inventory-tomcat-wrapper.log in the timeframe of the VCF workflow:INFO | jvm 1 | YYYY/MM/DD hh:mm:ss | java.lang.OutOfMemoryError: Java heap space
STATUS | wrapper | YYYY/MM/DD hh:mm:ss | The JVM has run out of memory. Requesting thread dump.
STATUS | wrapper | YYYY/MM/DD hh:mm:ss | The JVM has run out of memory. Restarting JVM.
...
INFO | jvm 1 | YYYY/MM/DD hh:mm:ss | # java.lang.OutOfMemoryError: Java heap space
STATUS | wrapper | YYYY/MM/DD hh:mm:ss | The JVM has run out of memory. Requesting thread dump.
STATUS | wrapper | YYYY/MM/DD hh:mm:ss | The JVM has run out of memory. Restart JVM (Ignoring, already restarting).
INFO | jvm 1 | YYYY/MM/DD hh:mm:ss | # -XX:OnOutOfMemoryError="gzip -f /image/core/cm_inventory_oom.hpro
VMware NSX-T Data Center
VMware NSX
During the VCF workflow, information about the vCenter cluster may be fetched multiple times and as a result cm-inventory saves the retrieved information multiple times which may lead to out of memory errors in larger setups.
This issue is resolved in VMware NSX-T Data Center 3.2.2 and NSX 4.0.1, available at Broadcom downloads.
If you are having difficulty finding and downloading software, please review the Download Broadcom products and software KB.
Workaround
/usr/tanuki/conf/cm-inventory-tomcat-wrapper.conf on the NSX Managers as root user and change wrapper.java.maxmemory line to have a value of 1024 as shown below:wrapper.java.maxmemory=1024
/etc/init.d/cm-inventory restart