Oracle Universal Connection Pool and WebLogic JDBC Data Source: Interoperability of Leak Detection and Timeout Settings
0 reputation · 06 Mar 2020, 05:13 UTC
Determine the optimal leak detection configuration when pairing Oracle Universal Connection Pool (UCP) with a WebLogic JDBC data source in an Oracle RAC deployment.
The goal is to prevent connection exhaustion while avoiding false‑positive leak reports, given that idle and inactive timeout handling varies between Oracle Database 12c and 19c and that RAC affinity can skew connection usage across nodes.
Uncertainty remains whether to rely on UCP’s connection leak proxy, WebLogic’s built‑in data source leak detection, or to enable both, and how timeout values should be coordinated to prevent premature eviction or connection storms under high load.
Which leak detection mechanism should be enabled to avoid false positives? How should idle and inactive timeout values be aligned between UCP and WebLogic to prevent premature connection eviction? Does enabling both mechanisms increase overhead or risk connection storms during peak concurrency?
oracle