Foglight Management Server is slow. Error: "java.lang.OutOfMemoryError: Java heap space" occurs. (4246690)

The Foglight Management Server (FMS) is very slow.

When trying to login to the console or display any dashboard, it can take several minutes to open.

Messages similar to the following appear in the FMS management server log:

FATAL [AgentManagementQuartzScheduler_QuartzSchedulerThread] com.quest.nitro.util.DefaultExceptionHandler - An unexpected error occurred which may cause undesired behavior. You may want to contact Quest Software customer support if you see this error again: Unhandled exception in thread "AgentManagementQuartzScheduler_QuartzSchedulerThread": "java.lang.OutOfMemoryError: Java heap space"

 Foglight Java Virtual Machine (JVM) is running out of memory.

Out of the box, Foglight allocates amount of memory for the JVM:

32-bit OS:

Min - 256mb
Max - 75% of total memory or 1024mb, whichever is less.

64-bit OS:

Min - 512mb
Max - 75% of total memory

This is documented in the following configuration file on the Foglight installation directory "$FOGLIGHT_HOME\config":
FMS 5.5.8 and earlier versions = "foglight.config"
FMS 5.6.2 and later versions = "server.config"

# The native launcher allocates the following defaults
# min heap max heap
# 32-bit: -Xms256m -Xmx{75% of total memory < 1024m}m
# 64-bit: -Xms512m -Xmx{75% of total memory}m

1. Increase the JVM heap memory size:

a. Go to "$FOGLIGHT_HOME\config" directory.
b. Make a backup copy of the configuration file:
     FMS 5.5.8 and earlier versions = "foglight.config"
     FMS 5.6.2 and later versions = "server.config"
c. Edit the existing configuration file (see above).
d. Look for the following settings:

FMS 5.5.8 and earlier versions:
# foglight.vm.option0 = "-Xms=1280m";
# foglight.vm.option1 = "-Xmx=1280m";

FMS 5.6.2 and later versions:
# server.vm.option0 = "-Xms=1280m";
# server.vm.option1 = "-Xmx=1280m";

FMS 5.5.8 and earlier versions:
Uncomment (remove '#' symbol) and change it if needed to the following two lines for a 32-bit FMS OS:
foglight.vm.option0 = "-Xms1280m";
foglight.vm.option1 = "-Xmx1280m";"

FMS 5.6.2 and later versions:
Uncomment (remove '#' symbol) and change it if needed to the following two lines for a 32-bit FMS OS:
server.vm.option0 = "-Xms1280m";
server.vm.option1 = "-Xmx1280m";"


Note: 64 bit FMS OS -Xms and Xmx do not have a limit of 1280m. They can be set to whatever is needed.

As an example of allocating 6GB to the JVM heap on a 64-bit FMS OS:

FMS 5.5.8 and earlier versions:
foglight.vm.option0 = "-Xms6144m";
foglight.vm.option1 = "-Xmx6144m";"

FMS 5.6.2 and later versions:
server.vm.option0 = "-Xms6144m";
server.vm.option1 = "-Xmx6144m";"

FMS 5.7.x and later versions:
server.vm.option0 = "-Xms6g";
server.vm.option1 = "-Xmx6g";"

Also see: SOL70101

Another area that can contribute to performance:

Make sure all Foglight user are using "Sign Out" instead of just closing user interface (UI).
"Sign Out" is in the upper right hand portion of the UI.
Just closing the browser window without using "Sign Out" leaves Java sessions open for 30 minutes, consuming memory resources.