Fglams disconnecting or the DB Cartridges cannot be enabled or the Admin Console timeouts (4310988)

Three problems occour randomly:

• Fglams disconnecting
• DB Cartridges will not enable
• Admin Console timeouts

The following message may also appear in the FMS 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
java.lang.OutOfMemoryError: Java heap space

The Foglight Management Server ran out of resources (memory, cpu).

Tuning the Foglight Java Virtual Machine (JVM)

Edit the
\$FMS_HOME\config\server.config file (foglight.config for FMS 5.6 and lower) - open in text editor look for the section:

# The native launcher allocates the following defaults
# min heap max heap
# 32-bit: -Xms{same as Xmx}m -Xmx{75% of total memory < 1024}m
# 64-bit: -Xms{same as Xmx}m -Xmx{75% of total memory < 4096}m
#
# Examples for specific memory overrides:
#
# Laptop-friendly
# server.vm.option0 = "-Xms512m"
# server.vm.option1 = "-Xmx512m"
#
# Minimum memory, VMWare image friendly
# server.vm.option0 = "-Xms128m"
# server.vm.option1 = "-Xmx512m"
#
# Maximum memory/production for 32-bit Windows
# server.vm.option0 = "-Xms1280m"
# server.vm.option1 = "-Xmx1280m"

The '#' character at the beginning means that that the line is commented out. So, the JVM memory settings default to what is explained in the commented comments:

# 32-bit: -Xms{same as Xmx}m -Xmx{75% of total memory < 1024}m

Above means that if Foglight is running as a 32 bit app, Foglight will allocate 75% of the total physical ram OR 1024 mb - whichever is less. 1024 mb is the maximum Foglight JVM allocation that can be set when Foglight is running as a 32 bit app.

# 64-bit: -Xms{same as Xmx}m -Xmx{75% of total memory < 4096}m

Above means that if Foglight is running as a 64 bit app, Foglight will allocate 75% of the total physical ram OR 4096 mb - whichever is less. There isn't a limit to the JVM memory that Foglight 64 bit can allocate.

To correct the issues for 64 bit (32 bit you cannot do much with):

Create the vm.options to set the JVM allocation manually. Use the next available vm.option number (0, 1, 2, etc) available...

FMS 5.7.5.x and higher:

server.vm.option0 = "-Xms6144m";
server.vm.option1 = "-Xmx6144m";

FMS 5.6.x and lower:

foglight.vm.option0 = "-Xms6144m";
foglight.vm.option1 = "-Xmx6144m";

Above changes/sets the JVM from the default max allocation of 4096m to 6144m.

Note: the semi colons at the end of each line are imperative - the FMS will crash if the semi-colons are not present. Save server.config file and restart FMS service to make changes take effect. Over time, run a Management Server Performance Report and check JVM memory usage - may need to increase even higher - may need to go to 8192m (8gb) if machine has it available.