Foglight server is slow to respond or becomes completely unresponsive. Incoming data from agents may be dropped. Problems when multiple users logged in simultaneously.
Errors in management server log file like this one:
YYYY-MM-DD HH:MM:SS.DDD ERROR [DataAccess-7-thread-4] com.quest.nitro.util.DefaultExceptionHandler - DefaultExceptionHandler.uncaughtException: [DataAccess-7-thread-4, java.lang.RuntimeException: org.jboss.util.NestedSQLException: No ManagedConnections available within configured blocking timeout ( 30000 [ms] );
Load on Foglight server is consuming all connections to the Foglight repository database.
This can be due in part to:
1) Users are not logging out of Web Console. Ex: The user is closing the browser instead of logging out. This can leave un-needed queries running continuously.
2) The database performance is poor. Slow response means connections are not released until task is finished. This can cause a 'bottleneck' affecting Foglight performance.
Increase available connections to the database
Note: Starting with Foglight 5.9.8 the maximum for JDBC connections was increased to 60 and will be used if the parameter is commented-out.
For FMS versions 5.9.1
Please refer to the Foglight Performance Tuning Field Guide.
This setting will increase the load on the Foglight database server. Please make sure that adequate resources for both the Foglight server as well as the database server hosting the Foglight repository are available.
Contact a sales person if professional services group are needed to help size the environment. This is beyond the scope of support.