The agent manager crashes in a period of time, and the following errors can be seen in the log of the agent manager:
WARN [Quartz-3407] com.quest.glue.core.LowMemoryListener - Memory recovery failed after high memory detected, and either 5 GC(s) or 60,000ms transpired (waiting for at least one GC). At the moment more than 90% (318.4 Mb out of 348 Mb) of the G1 Old Gen memory pool is in use. It is possible that this instance of the Agent Manager may run out of memory. This may be the result of too many agent instances or agent instances consuming more memory than the Agent Manager is currently configured to provide. Consider decreasing the number of agent instances, or increasing the amount of memory allocated to the Agent Manager.
INFO [Quartz-3407] com.quest.glue.core.performance.ErrorMessageReporter - WARN message starting with "Memory recovery failed after [ ...]" has been transmitted upstream.
ERROR [Startup Thread] com.quest.glue.common.util.MessageValidationHandler - A fatal error was encountered while validating the XML structure: Premature end of file. at line 1 [line 1, column 1]
The baseline.jvmargs.config is not properly configured.
In consequence, the agent manager runs out of memory because the information of vmparameter.0, vmparameter.1 and vmparameter.2 parameters from baseline.jvmargs.config file cannot be loaded.
Modify the file baseline.jvmargs.config file (%FglAM_HOME%\state\default\config\baseline.jvmargs.config) with the needed format for each parameter. Example:
vmparameter.0 = "-Xms4096m";
vmparameter.1 = "-Xmx4096m";
vmparameter.2 = "-Dcom.quest.connection.regulator.maxActiveConnectionsCap=1024";
Next make sure there is no typo or invalid character which can break the configuration file.
Once the settings have been corrected please restart the agent manager.