Question
Pegasystems Inc.
IN
Last activity: 23 Mar 2020 3:57 EDT
Pega managed DB connection pooling sizing based on nodetype
In Pega 831, it was observed that, if JDBC URL is used in DB connection rule, Pega creates 20 (default) DB connections per JVM/server. This can be managed using DSS or prconfig.xml.
In case of pega cloud environment, where custom prconfig.xml per node is not allowed, how to control number of connection established, (as part of connection pooling) based on nodetype.
For example, If requirement is to have 20 connections from web nodes, background processing nodes and zero connections from other node types, how this can be achived.
NOTE: As mentioned above, in Pega Cloud environment, having custom prconfig.xml per node is NOT an option. Single copy of prconfig.xml is used on all nodes of a environment.
Pegasystems Inc.
US
In pegacloud, the main pega databases (pegadata,pegarules) are using tomcat connection pool, which should be managed by Pega. Keep in mind that, this is different from a database accessible through JDBC URL (e.g., ExternalMKTData or any other external database connected through URL), which uses hikari connection pool (since Pega 7,4, there are several DSS related to this as you have mentioned: e.g., https://community.pega.com/knowledgebase/articles/database-management/hikaricp-connection-pool-configuration)
Any effort to adjust Pega tomcat connection pool (which has been set a fairly high number already) should go through Pegacloud team - clients should not have to worry about that.
Pegasystems Inc.
IN
Hi kevin,
I am not trying to modify connection pool for Pega( or pega database). My question is around custom external DB connections( not Pega DB), where customer has created DB rule to connect to external database as per requirement.
Can customer limit no.of connections created, per nodetype.
Thanks
Suhas