ColdFusion Database Connection Pool Exhausted

ColdFusion connection pool exhaustion occurs for eight primary documented reasons: the “Restrict connections to” setting in ColdFusion Administrator is lower than concurrent traffic demands; application code leaks connections by leaving queries, transactions, or ORM sessions unclosed; long-running queries without timeout attributes hold connections indefinitely; cfthread background processing spawns connections that never return to the pool; the database server's own max_connections limit sits below the ColdFusion pool size; stale or dead connections accumulate because "Validate Connection" is disabled; idle connection cleanup is misconfigured and ColdFusion only closes five connections per interval by design; and ColdFusion does not use the connection pool when issuing KILL QUERY commands — it creates a brand new connection that itself consumes pool capacity. The fix requires tuning datasource configuration, eliminating leaks at the code level, and aligning pool limits across every layer of the stack.

Read More