Users can try to increase the timeout to perhaps 300000 by following the steps below:
- Go to "Administration | Agents | Agent Status"
- Select the problematic agent and click on "Edit Properties"
- Now click on the link "Modify the properties for this agent only"
- Update the 2 parameters
"DB Connection Timeout (milliseconds)"
"On-Demand DB Query Connection Timeout (milliseconds)"
- Click on "Save"
- Finally deactivate and active the agent to force the change pushed out to the agent.
For troubleshooting:
- confirm the database server is running
- check the port is correct
- check that the server has sufficient processing capability
- review the network connection to the server from the FglAM
- try an external java based application to connect to the Replication server
However this is just the initial connection to the host, unless the performance on the server is reviewed other collections will likely also timeout during monitoring.