Timedout (90000 ms) while trying to acquire a permit for connection (0 available permits of {current_limit}) (4300105)

This occurs when the Agent Manager cannot obtain a connection permit within the timeout period. The value {current_limit} represents the configured maximum number of concurrent permits (maxActiveConnectionsCap), which varies by environment.

The FglAM uses the JVM parameter:

This parameter limits the number of concurrent OS-level connections (permits) the Agent Manager can hold.

• Default value: 200
• If the environment has many agents or slow connection release, permits can be exhausted, causing timeouts.

Resolution 1: Increase maxActiveConnectionsCap

1. Go to the installation path on the Agent Manager host ([FGLAM_HOME]\state\default\config)
2. Edit the baseline.jvmargs.config file.
3. Add or modify:

   vmparameter.X = "-Dcom.quest.connection.regulator.maxActiveConnectionsCap={new_limit}"
   

   • Replace X with a unique index.
   • Replace {new_limit} with a value higher than the current setting (e.g., 1024).
4. Restart the FglAM service or daemon.

Resolution 2: Reduce concurrent connections

Disable unnecessary collections to free up permits:

• WindowsAgent: Disable Collect Log Events if the Event Log rule is disabled.
• Infrastructure Cartridge agents: Disable CPU, Disk, Memory, and Network metrics for VMs already monitored by VMware or Hyper-V agents.