Question
HCL Tech
IN
Last activity: 3 Oct 2025 18:22 EDT
Does Pega reconnects without a JVM restart during DB interruptions/glitch.
Hello Pega Community,
Is Pega will reconnects automatically by itself whenever there is a DB Outage.
Consider that the DB outage is not for so long, for suppose if DB went down for a minutes of time (might be a half min also ) , for these type of situations DB having a feature called TAC (Transparent Application Continuty) that will helps the App will auto connect and avoid a separate jvm restart. So will Pega Supports this feature if yes what are the App settings we need to configure from Pega side to eliminate a JVM restarts.
HCA Healthcare
US
yes, Pega will usually reconnect without a JVM restart if the database blips, because connections are managed by the app server’s JDBC pool. To make this reliable, point your Pega datasource at a HA endpoint (Oracle RAC SCAN/service name) and use the current Oracle JDBC driver. Turn on connection validation in the pool (test-on-borrow/return/idle with a simple validation query like select 1 from dual) and enable eviction of dead connections (idle/abandon settings). Set reasonable socket/login timeouts and JDBC URL retries. If your DBA enables Oracle Application Continuity/Transparent Application Continuity on the service, Pega benefits automatically—no Pega code change—so long as the driver and service are configured for FAN/ONS. For Kubernetes, let readiness/liveness probes recycle only the bad pod, not the whole cluster. In Pega Cloud this is already tuned; on-prem, mirror those settings in your app server (Tomcat/WebSphere/JBoss) datasource. Caveat: very long or repeated outages can still force node recovery, but brief glitches should self-heal.