Question
TSPI
US
Last activity: 24 Aug 2020 23:26 EDT
Dynamic System Setting for Database Idle Connections
We have a pega cloud instance with external database connections configured in designer studio. We have been getting incidents created saying pega is creating many idle connections to this data base. I found a setting to set max connections using Dynamic System Settings and an article saying Idle settings have been added as of 8.1 but I can't find those settings. Is there any documentation on the list of allowed Dynamic System Settings? If not could I at least get any connected with database connections.
Article mentioning updated functionality - https://community.pega.com/node/716556
Pegasystems Inc.
AU
KCI
IN
Hi,
We are facing the same issue: too many inactive sessions in external database.
We have limited the pool size and time out using dss.
Any reason why Pega is not closing the inactive sessions.
Thanks
Hi Michael,
The article that you are referring to is related to SOAP requests. All the SOAP requests will sit in Axis2 connection pool. Pega will close and delete the connections from the Axis2 connection pool that have been idle for the time specified by Axis2_idleTimeout DSS entry or for 1800000 milliseconds by default if this DSS is not set.
Coming to your question regarding killing the idle session, set the connection pool size to an appropriate default size. If needed adjust the pool size from the default on specific nodes.
The default will be used for all nodes which do not have a node-specific DSS value for this property.
prconfig/database/databases/yourDBInstanceName/connectionPoolSize/default
For node specific settings the format will be like the following with nodeID replaced with the actual nodeID.
prconfig/database/databases/yourDBInstanceName/connectionPoolSize/nodeID