Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Troubleshooting: PEGA0026 alerts indicate connection pool settings too low

Updated on September 25, 2019


Many instances of the critical alert PEGA0026 occur in the PegaRULES Alert log and in the PegaRULES Log.

PEGA0026 Time to connect to database exceeds limit

This alert often indicates that the connection pool settings for the PegaRULES database require adjustment to improve performance.

The instructions below are for Oracle products. Details for adjusting the connection pool settings differ by platform

Example: WebLogic 10 with Oracle 10g database

The application server is Oracle BEA WebLogic Version 10 running on Solaris with two WebLogic JVMs clustered. You have specified a connection pool to connect to the PegaRULES database using Oracle 10g. The database connection pool has an initial size of 70 connections with the maximum connections set to 125 for a total of 310 users.

Initial Connection Pool settings might look like this example:

JNDI Name: jdbc/PegaRULES
Row Prefetch Enabled false
Row Prefetch Size: 48
Stream Chunk Size: 256
URL - jdbc:oracle:thin:@your_database_URL_used_to_create_the_connections_ in_this_Connection_Pool
Driver Class Name: oracle.jdbc.OracleDriver
Properties: oracle.jdbc.V8Compatible=true user
Initial Capacity: 70
Maximum Capacity: 125
Capacity Increment: 10
Statement Cache Type: LRU
Statement Cache Size: 10
Test Connections On Reserve: true
Test Frequency: 120
Seconds to Trust an Idle Pool Connection: 10
Shrink Frequency: 900
Connection Creation Retry Frequency:0
Login Delay: 0
Inactive Connection Timeout: 120
Maximum Waiting for Connection: 2147483647
Connection Reserve Timeout: 10
Statement Timeout: -1
Ignore In-Use Connections: true
Pinned-To-Thread: false
Remove Infected Connections Enabled: true


Suggested Approach

To reduce or eliminate the number of PEGA0026 alerts, take the following actions:

  1. Set the initial connection pool size to match the total number of connections created during the performance test.  In the example above, the setting for Initial Capacity should be 125 to match the Maximum Capacity.

  2. This ensures that all the required connections are obtained up front when the WebLogic application server starts.

  3. After you have adjusted and tested the connection pool settings, turn on the setting Test Connection on Reserve to ensure that the connection is not destroyed or lost when the connection is idle in the pool.
  4. By properly configuring connection pools in your WebLogic Server domain, you can improve application and system performance. Refer to the Oracle/BEA WebLogic Server Administration Console Help topics on tuning data source connection pool options that are cited as references below.

Related Topics

Understanding the PEGA0026 alert - Time to connect to database exceeds limit

  • Previous topic Troubleshooting: Out-of-the-box triggers reference pr_sys_locks table impacting PRPC performance (HFix-4229, HFix-4349)
  • Next topic Troubleshooting: PSYSLOCK MAXROWS=1 causes poor performance (DB2 10 for z/OS)

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us