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.

Configuring the number of database transaction retries

Updated on November 29, 2016

You can configure the number of retries for database transactions that fail because of database or network outages on high-availability systems. The ability to retry database transactions is available for Pega Cloud customers using a Postgres database and for on-premises customers using a Pega-supported database that supports database failover.

You can set the number of retries for PegaRULES, PegaDATA, and for other databases, to a value of 0 to 3, where 0 means that retries are turned off. The default value for the number of retries is 3 for PegaRULES and PegaDATA, and 0 for other databases. Changing the number of retries might be useful during troubleshooting; however, the default values should not need to be changed during normal operations.

To change the number of retries, add or edit the value of the following settings in the prconfig.xml file:

<env name="database/databases/PegaRULES/retryAttempts" value="3"

<env name="database/databases/PegaDATA/retryAttempts" value="3"

<env name="database/databases/<other database name>/retryAttempts" value="3"

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us