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.
PRPC may open many database connections to the PegaRULES database. When started, the system opens two connections. To provide good response to requestors, the system uses a pool of connections over time. In most cases, the pool is created and managed by the application server such as WebSphere, not by PRPC, but the prconfig.xml settings described here control the size of the pool and the timeout interval.
If database access is later needed at a moment when all existing connections are busy, the system creates an additional connection. Connections remain open until PRPC is stopped, or until they are idle for 5 minutes or longer. (The value of IdleConnectionTimeout in the prconfig.xml file defines the interval, in seconds, after which an idle connection is marked to be closed.)
As initially installed, the system does not limit the number of open connections created. Using an optional setting in the prconfig.xml file, you can limit the size of this pool:
1. Open the prconfig.xml file with an XML editor or text.
2. Locate the PegaRULES database username and password entries.
3. Add the following
<env name="database/databases/pegarules/maxConnections"
value="20"/><env name="database/databases/pegarules/maxConnectionsTimeout"
value="30"/>
to limit the size of the pool to 20 connections, and cause a Java exception if the connection pool is empty for 30 seconds when a requestor is waiting.
4. Save the updated file. Undeploy and redeploy to make this change effective.
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.
However, if the limit is reached and all connections are busy when an additional database request arrives, the requestor waits. After 10 seconds (or another interval set in the maxConnectionsTimeout value), if no connection is available, a Java DatabaseException is thrown.
Don't set this limit too low, or deadlocks and poor response may result. You can set a threshold for PEGA0026 alerts to detect long waits.
For more information, see PDN article How to set the maximum number of JDBC connections to the PegaRULES database.
|
PegaRULES database |
|
About Database data instances
How to detect long database connection waits Working with the PegaRULES database |
SysAdmin category