NetBeans JDBC Connection Pool Configuration Lacks Configurable Wait Timeout

Answer to the Core Question

Yes – NetBeans should expose a user‑configurable wait‑timeout (or acquisition timeout) in the Services window pool editor. In its absence, the IDE relies on the JDBC driver’s default behaviour, which can block the UI indefinitely when the pool reaches its maximum size. A sensible default timeout, combined with clear documentation that the actual semantics are driver‑dependent, would prevent UI hangs and give developers predictable control.

Why a Wait‑Timeout Matters

When a connection pool is exhausted, a request for a new connection normally blocks until a slot frees up. If the IDE’s UI thread performs this blocking call, the entire interface freezes, making debugging impossible. A configurable timeout turns a silent block into a recoverable error that can be surfaced in the Output pane or as a notification.

Current State (Confirmed)

• The pool editor exposes Initial Size, Maximum Size, and Statement Cache only.
• No UI field for acquisition timeout exists in NetBeans 24.x or earlier.
• When the pool is full, the IDE may block indefinitely; the log shows messages like "Connection acquisition timed out" only if the underlying driver implements a timeout.

Suggested Enhancements (Likely)

• Add a Wait‑Timeout (seconds) field to the pool editor with a default value of 30 s.
• Document that the timeout is honoured only if the JDBC driver supports it; otherwise the IDE falls back to the driver’s default behaviour.
• Expose a Pool Exhaustion Policy toggle: Fail Fast (throw an exception immediately) vs Wait With Timeout (block up to the timeout).
• Show a non‑blocking status icon next to the pool in the Services view when exhaustion is detected.
• Log a clear warning to the Output window when a timeout occurs: "Connection acquisition timed out after 30 s – pool exhausted; consider increasing maximum size or reducing concurrency."

Practical Work‑Arounds for the Current Release

1. Adjust Pool Size – Temporarily increase Maximum Size in the editor to accommodate peak concurrency.
2. Use Driver Properties – Many drivers support a loginTimeout or socketTimeout property. Add it to the connection URL or properties file. Example for PostgreSQL: ?loginTimeout=30.
3. Run Queries Asynchronously – If you are executing database tasks from a UI action, wrap the call in a SwingWorker or background thread to avoid blocking the EDT.
4. Monitor Logs – Open View > IDE Log or the Output pane for messages about pool exhaustion. They usually contain the stack trace of the blocking thread.
5. Use External DataSource – For heavy workloads, consider configuring an external connection pool (e.g., HikariCP) in a db.properties file and point NetBeans to it via a JDBC URL.

Diagnostic Detail Needed

To tailor the recommendation further, could you provide the JDBC driver name and version you are using, as well as the NetBeans IDE version? Different drivers (e.g., Oracle, MySQL, PostgreSQL) expose timeout properties differently, and newer NetBeans releases may already include hidden settings.