Details

The Java Runtime environment can cause a memory leak or lock files under certain conditions. Without memory leak protection, Performance Chart can continue to consume system resources that will lead to ‘OutOfMemoryErrors’ when reloading web applications.

Memory leaks occur when JRE code uses the context class loader to load a singleton. This will cause a memory leak if a web application class loader happens to be the context class loader at the time. The ‘JreMemoryLeakPreventionListener’ class is designed to initialize these singletons when Tomcat’s common class loader is the context class loader. Proper use of JRE memory leak protection will ensure that the hosted application does not consume system resources and cause an unstable environment.

Solution

Navigate to and open /usr/lib/vmware-perfcharts/tc-instance/conf/server.xml.

Navigate to the node.

Add ‘‘ to the node.

Supportive Information

The following resource is also helpful.

• https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_VMW_vSphere_6-7_STIG.zip

This security hardening control applies to the following category of controls within NIST 800-53: Configuration Management.This control applies to the following type of system Unix.

References

• 800-53|CM-7a.
• CAT|II
• CCI|CCI-000381
• Rule-ID|SV-239415r674968_rule
• STIG-ID|VCPF-67-000014
• Vuln-ID|V-239415

Source

• Tenable.com/audits