Error: java.lang.OutOfMemoryError

Technical Articles ID: KB71516
Last Modified: 2022-03-02 01:48:30 Etc/GMT

Environment

McAfee ePolicy Orchestrator (ePO) 5.x

Problem

The Orion.log file contains the following error:

Error: java.lang.OutOfMemoryError

The following issues can occur when this error displays in the Orion.log file:

ePO console is unresponsive or slow.
DataChannel requests are not processed.
ePO server tasks are not executed until services are restarted.
ePO console default dashboard does not display or load.

Cause

The error GC overhead limit exceeded occurs if:

Too much time is spent in the Garbage Collection. For example, More than 98% of the total time in garbage collection.
And
If less than 2% of the Heap is recovered.

If the above conditions are met, an OutOfMemoryError is sent.

The above feature is built into the Java virtual machine, designed to prevent applications from running for an extended period. While making little or no progress, because the heap is too small.

The error java.lang.OutOfMemoryError: Java heap space, most likely occurs for the following reasons:

The Java application has a memory leak. (In this case, an extension that was loaded is leaking memory.)
The Java application (Tomcat/ePO) needs more memory than the default to run properly. Some extensions, such as Drive Encryption, and Host Intrusion Prevention (Host IPS), might require extra memory in the heap to run correctly and faster.

Solution

If the Workaround provided below does not resolve the issue:

A Java heap dump from the ePO server is needed for escalations to Technical Support.
For instructions to generate a Java heap dump when ePO encounters an OutOfMemory error in ePO Orion.log, see Solution 1 of KB73309.

To contact Technical Support, go to the Create a Service Request page and log on to the ServicePortal.

If you are a registered user, type your User ID and Password, and then click Log In.
If you are not a registered user, click Register and complete the fields to have your password and instructions emailed to you.

Workaround

Increase the Mmaximum Java Memory Pool size in the registry on the ePO Application Server:

CAUTION: This article contains information about opening or modifying the registry.

The following information is intended for System Administrators. Registry modifications are irreversible and could cause system failure if done incorrectly.
Before proceeding, Technical Support strongly recommends that you back up your registry and understand the restore process. For more information, see the Microsoft Windows registry information for advanced users article.
Do not run a REG file that is not confirmed to be a genuine registry import file.

Press Windows+R, type regedit, and click OK.
Navigate to and expand the registry key below:

32-bit servers:
HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Procrun 2.0\MCAFEETOMCATSRV200\Parameters\Java

64-bit servers:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Apache Software Foundation\Procrun 2.0\MCAFEETOMCATSRV250\Parameters\Java
Select the Java sub-key.
Increase the JvmMx parameter value.
ePO 5.x uses a 64-bit Java Runtime Environment. Which means that you can set the JvmMx parameter to a much larger value than in ePO 4.x. Set JvmMx to a value equal to at least 50% of the available system memory. For environments with larger numbers of endpoints, the recommended minimum of 8 GB for ePO 5.x might not be enough. Make sure that sufficient memory is available for other resident processes such as an Agent Handler or Event Parser. The operating system itself needs about 10% of the available memory.

NOTE: By default the JvmMx parameter accepts an integer value that represents the number of megabytes. For example, to set this parameter to 16 GB, the value to enter would be 16384.

Affected Products

Languages:

This article is available in the following languages:

Knowledge Center

Error: java.lang.OutOfMemoryError

Environment

Problem

Cause

Solution

Workaround

Affected Products

Languages:

Title

Title

Knowledge Center

Error: java.lang.OutOfMemoryError

Environment

Problem

Cause

Solution

Workaround

Affected Products

Languages:

Choose your region

Title

Title