How to detect long database connection waits (PEGA0026 alert)
How to detect long database connection waits (PEGA0026 alert)ALIBJ 5.4 Every requestor frequently uses database connections to the PegaRULES database, and may also access external databases. The ability of a requestor to acquire a database connection quickly when needed can affect overall performance.
Through prconfig.xml settings, you can cause a system alert to appear when this wait exceeds a threshold value, expressed in milliseconds. Separate threshold settings apply to initial connections (when account details and passwords are sent) and to reuse of existing connections.
When the requestor waits too long for either an initial connection or to reuse an existing connection, an alert occurs:
PEGA0026 Time to acquire a connection has exceeded the alert threshold of 100 ms. NNN ms.
where NNN is the actual time in milliseconds. Additional details in the alert message include the database name and whether the connection is initial or established.
If this alert appears often, especially periods of during peak demand, consider increasing the size of your database connection pool. See PDN article Understanding the PEGA0026 Alert.
This facility is enabled by default, with a threshold of 100 milliseconds for established connections and 10,000 milliseconds for initial connections. To establish other thresholds:
1. Update the alerts section of the prconfig.xml file, setting a longer or shorter desired threshold in milliseconds:
<env name="alerts/database/acquireConnectionAlertMS" value="nnnn" />
<env name="alerts/declarative/lookupTime/thresholdMS value="nnnn" />
where nnnn is a positive integer in milliseconds.
2. Stop and restart the server.
As an alternative to the prconfig.xml file, you can use Dynamic System Settings to configure your application.
See How to create or update a prconfig setting.
|
alert log |
|
Understanding alerts
How to limit connections to the PegaRULES database |
SysAdmin category