Custom connection properties required for disaster recovery
To maintain the stability of your Pega application in the case of a network or database outage, your application must have an appropriate recovery time to clean up broken connection sockets caused by the outage.
In Pega Cloud environments, Pega manages the connection properties settings to provide application stability across the fleet of systems. Pega Cloud clients cannot change, or request changes, to the default connection property configuration.
On-premises and client-managed cloud clients must configure the recovery time in your application server on a node-by-node basis, using the custom connection properties appropriate for your database. You complete the appropriate configuration during the Pega Platform installation or update process by referring to your application server’s documentation:
Recommended custom JDBC connection properties to ensure connection recovery
| Database type | Socket timeout setting | Connection Timeout |
| Postgres | socketTimeout=90 | Not applicable |
| MSSQL | socketTimeout=90000 | Not applicable |
| Oracle | oracle.jdbc.ReadTimeout=90000 | oracle.net.CONNECT_TIMEOUT=10000 |
| DB2 | blockingReadConnectionTimeout=90 | connectionTimeout=10 |
Because these socket timeout and read timeout setting combinations in your application server cause a global query timeout, you should evaluate the effect of these settings on your application to ensure that your application meets requirements using these settings. For example, if you are using Pega Customer Decision Hub, the ExternalMKTData database requires a longer recovery time compared to the Pega database in your database setup.
Previous topic Connection pool settings Next topic Database tables and views