Example connection pool congestion entries from an uptime.log file:
2010-05-09 15:59:16,447 WARN (RealSessionFactory:63) - Connection pool congestion: busy: 450 idle: 50 total:500 maximum: 500 2010-05-09 15:59:16,447 WARN (RealSessionFactory:63) - Connection pool congestion: busy: 450 idle: 50 total:500 maximum: 500
These warning messages indicate that Uptime Infrastructure Monitor is losing time waiting for available connections to the DB. These messages are generally not an indication of a significant problem if they occur intermittently and in short bursts. However, if these messages are sustained for extended periods of time, please contact Uptime Customer Support for guidance on potential system tuning.
There are various reasons why you may be seeing these messages:
- The connectionPoolMaximum variable in the uptime.conf file is set too low (note that changes to this setting are often required as your installation expands).
- The connectionPoolMaximum variable in the uptime.conf file is set lower than the serviceThreads parameter. Note that the connectionPoolMaximum value should be at least 10% higher than the serviceThreads value.
- The connectionPoolMaximum variable in the uptime.conf file is larger than the number of actual connections available from your database server.
- Your Database may simply need additional tuning to accommodate the Uptime Infrastructure Monitor workload.