JDBC Connection Pool Exhaustion: Need Clarity on Connection Idle Timeout Settings

Background

Oracle Fusion Middleware uses WebLogic Server’s JDBC connection pool. When idle connections are not returned or the pool’s max capacity is too low for traffic spikes, the pool can exhaust, causing intermittent application failures. Default validation uses "SELECT 1 FROM DUAL" and there is no auto‑scaling; administrators manually adjust Max Capacity or enable newer dynamic pooling features.

Unresolved Decision

The product documentation does not specify how to configure the Connection Idle Timeout for long‑running batch jobs, leaving uncertainty whether idle connections should be closed aggressively or kept alive to avoid exhaustion during peak periods.

Key Questions

• What is the recommended idle timeout value for batch processes to balance resource usage and prevent pool exhaustion?
• How does setting a longer idle timeout affect memory consumption and licensing in WebLogic 12c versus 14c?
• Should the idle timeout be coupled with a specific validation strategy (checkout vs. return) to mitigate stale connections?