The vm.config file is missing in a FglAM configuration higher than 5.6.10.
How can a user adjust the -Xms/-Xmx memory configuration?
There has been a change to the FglAM configuration fileset (as outlined in the 5.6.10 FglAM documentation) in that the prior vm.config file has been removed and replaced with two new configuration files.
During an upgrade to 5.6.10, any vmparameter settings that were declared in the vm.config will be migrated to the new baseline.jvmargs.config file.
The new client.config retains the core FglAM configuration settings. Things like enabling IPv6, setting the path to java.vm, etc; have been moved here. You probably won't edit this file too often as most of the config setting here are fairly low level and have very specific needs in order for them to be changed.With Agent Negotiation now in play, you will only need to manage memory configuration when FglAM needs to support a cartridge deployment that does not declare resource settings in it's deployment config. In order to do so, we added a new configuration file: baseline.jvmargs.config (/config/client.config and /config/ baseline.jvmargs.config). When declaring memory setting here, these values are now considered as baseline memory needs and will be used as a starting/baseline to negotiated memory requires. (Note: There is a fairly lengthy comment in this file that discusses in far more detail on the usage and implication of setting parameters here.)
For example, if you declared -Xmx1024m in the baseline.jvmargs.config, when FglAM launches, it will allocated a max heap of 1024m. Let's also say that this system has 2048m of physical memory installed. Should at some point a new agent is deployed to FglAM that requests an additional 512m of heap, this value will be appended to the memory configuration that was declared as the baseline. So when FglAM negotiates the memory increase, it must evaluate with the baseline and deployment request fall within the physical memory parameters. As in this example they do; 1024m + 512m = 1536m; FglAM will restart with the new allocated heap size.
Example entry in baseline.jvmargs.config:
vmparameter.0 = "-Xms512m";
vmparameter.1 = "-Xmx1024m";
How the Agent Manager Applies Configuration Settings
Pg 55 of 113
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center