DataGrip Connection Pool: Unbounded Max Size and Idle Handling

DataGrip Connection Pool Configuration

DataGrip relies on the underlying JDBC driver to manage pooled connections. When the Max Pool Size field in the Data Source settings is left blank, the driver’s default is applied – often an unlimited value. Because DataGrip does not automatically close idle connections, the pool can grow until the database server’s connection limit is reached, causing intermittent failures for concurrent sessions.

Key uncertainties:

• The absence of a hard limit means DataGrip may open an unbounded number of connections under heavy load.
• Idle connections remain open indefinitely, with no built‑in cleanup or minimum idle threshold.
• Connection Timeout only limits the time to establish a new connection, not the lifetime of pooled connections.

To prevent exhaustion, we need to understand:

• Should DataGrip enforce a default maximum pool size when the field is empty?
• Can we configure DataGrip to automatically close idle connections after a configurable period?
• What mechanisms exist to monitor real‑time pool usage within DataGrip?