"client.config' does not exist and will not be loaded" and out of memory error (4210827)

When upgrading a multi-state FglAM's (Foglight Agent Managers) that share "bin" directories some of the agents managers becomes unresponsive as the states are running out of memory.

Out of memory messages appear in the logs. In addition error messages like the following appear in the agent manager log:

Foglight_Agent_Manager\state\default\config\client.config does not exist and will not be loaded.
Foglight_Agent_Manager\state\default\config\baseline.jvmargs.config does not exist and will not be loaded.

Defect FAM-5600 As the baseline.jvmargs.config is missing the Fglam  ignores the settings on vm.config file and starts up with Xmx256m -Xms22m heap size.

When upgrading an FglAM both files client.config and baseline.jvmargs.config  should be created in the %FGLAM HOME\state\\config directory.
When FAM-5600 is encountered the files are not created.

STATUS: Workaround documented below.

WORKAROUND documented in FglAM vm.config file migration fails under multi-state installations

1). Copy the client.config and baseline.jvmargs.config files from a working FglAM to the %FGLAMHOME%\state\\config directory

2). Update the copied baseline.jvmargs.config file with any modifications to the parameters (vmparameter.*) in the vm.config file.

3). Restart the FglAM.