Return
-
Title
VMWare agent not activatable after setting up maximum JVM heap size -
Description
User is unable to monitor VMWare environment as agent is not activating after setting up maximum JVM heap size.Agent Manager logs:---2021-03-11 13:12:43.592 ERROR [FglAM:IncomingMessage[5]-43] com.quest.glue.core.deployment.DeploymentManager - Failed to build an AgentPackage from D:\ Foglight Agent Manager\agents\VMwarePerformance\5.8.0-5.8.0-20190807-0724-796\config\agent.manifest. Cause: The addition of 3 GB to the negotiated JVM Max heap size would adjust to 13 GB, which would exceed the total available physical memory of 10 GB. Rejecting memory request.com.quest.glue.core.resources.InvalidResourceSettingException: The addition of 3 GB to the negotiated JVM Max heap size would adjust to 13 GB, which would exceed the total available physical memory of 10 GB. Rejecting memory request.2021-03-11 13:12:43.596 ERROR [FglAM:IncomingMessage[5]-43] com.quest.glue.core.comms.handlers.DeployAgentArchiveListener - Failed to deploy agent archive---There is 12 GB of RAM available on the Foglight Agent Manager (FglAM) server.The maximum JVM heap (xmx) is set to 10 GB.The starting JVM heap (xms) is set to 8 GB.
Sign In Required
You need to be signed in and under a current maintenance contract to view premium knowledge articles.