-
Title
Duplicate: FMS Memory Heap Incremental -
Description
Increase the FMS Memory Heap Incremental -
Cause
Process Heap Use
When a thread is created and run, a run-time stack is dynamically allocated from the native process heap (not the Java heap). This native heap requires a large contiguous memory block. If the system you are running does not have enough RAM, or if the operating system cannot find a large enough contiguous memory block, new native threads cannot be created and a java.lang.OutOfMemoryError occurs. If the VM generates errors relating to a failure to allocate native resources, or relating to exhaustion of process address space, you must increase the native process heap size. Errors appear as a Java VM internal error message or a detail message associated with an out-of-memory error. Messages with the relevant errors indicate that the problem is process heap exhaustion. This cannot directly set the size of the process heap. The process heap uses memory within the 32-bit address space not used by the garbage-collected heap. To increase the size of the process heap, decrease the maximum Java heap size using the -Xmx option in the server.config file.Setting Memory Parameters for the ServerSet the Memory Parameters for the FMS, over the Java Virtual Machine (JVM) the minimum and maximum memory parameters for the server are in the <foglight_home>\config\server.config file. If the installation supports a large number (100s) of Agents, Quest suggests you set the Java heap -
Resolution
If running the Management Server by running bin/fms,the configuration of the Java Virtual Machine’s (JVM’s) with minimum and maximum memory parameters for the server in the <foglight_home>/config/server.config file.
Starting Foglight using the run.[bat|sh] command, the JVM heap memory parameters set in the <foglight_home>/config/server.config file do not take effect. Use -X options to pass the memory parameters straight to the VM.
If the installation supports a large number (100s) of agents, Quest suggests to set the Java heap memory minimum (-Xms) and maximum (-Xmx) options to the same size. For example, assigning 1 GB of memory can be set in the server.config file as follows:
server.vm.option0 = “-Xms1280M”;
server.vm.option1 = “-Xmx1280M”;This parameter can be found as mentioned on the "server.config" file under:
Uncomment the following lines starting with option0 to adjust VM settings
#
# server.vm.option0 = "";
# server.vm.option1 = "";
# ...
# server.vm.option99 = "";
Ensure that you uncomment these lines in the file. The environment can be set up to 100 VM options in total.
Note:
The -Xms and -Xmx options are different for 32-bit and 64-bit JVMs and available physical memory.
The values of the -Xms and -Xmx options do not necessarily have to be the same size. However, the value of the -Xmx option should not exceed certain limits as determined by the System Administrator.