IntelliJ Database Connection Pool Size Change in 2026.1: Unresolved Idle-Connection Eviction Policy
0 reputation · 23 Aug 2022, 23:33 UTC
Problem Context
In IntelliJ IDEA 2026.1 the Database tool introduced a per‑connection pool size setting under File > Settings > Database > Data Sources > Advanced. The default remains 30 connections unless overridden. Despite this, idle connections are not automatically evicted; they persist until the IDE terminates. This can lead to intermittent connection‑pool exhaustion in large or long‑running projects.
Goal and Constraints
The goal is to diagnose and prevent intermittent exhaustion of the JDBC connection pool. Constraints include: the new pool size setting is only available in 2026.1+, there is no UI for monitoring active connections, and idle‑connection eviction is not yet configurable. Verification requires external monitoring or IDE logs.
Unresolved Decision
IntelliJ’s documentation does not clarify whether an idle‑connection eviction policy will be added, nor how the pool behaves across multiple database consoles or projects.
Specific Questions
- Should IntelliJ introduce a configurable idle‑timeout or automatic eviction policy for database connection pools?
- What mechanisms can developers use to monitor active pool usage in the absence of a built‑in UI?
- Does the pool size setting apply globally across all database consoles for a data source, or is it isolated per console?
