An administrator is observing slow performance of the vCenter Inventory Service and observes the entries from the wrapper.log file: Exception in thread "tomcat-exec-2" java.lang.OutOfMemoryError…

In vSphere 6.x, the Inventory Service JVM heap size is automatically calculated based on the total available system memory of the vCenter Server host. Increasing the physical or virtual memory resources of the vCenter Server machine allows the Inventory Service to claim a larger heap, resolving the OutOfMemoryError without manual JVM tuning.

cloudvm-ram-size is a VCSA sizing parameter that sets the overall memory profile for the appliance, but it does not directly resolve a JVM heap exhaustion issue in the Inventory Service when memory resources are the underlying constraint.

The Platform Services Controller handles authentication and licensing services and does not host the Inventory Service; adding memory to the PSC has no effect on Inventory Service heap allocation.

Manually editing wrapper.java.maxmemory in wrapper.conf was the approach for vSphere 5.x, but in vSphere 6.x the heap is auto-managed based on system RAM, so the root fix is to increase available host memory rather than hardcoding a JVM parameter.