NetBeans JDBC Connection Pool Configuration Lacks Configurable Wait Timeout

Goal: Prevent the NetBeans IDE UI from blocking indefinitely when a JDBC connection pool is exhausted during concurrent database operations.

Constraint: The connection pool editor in the Services window exposes initial size, maximum size, and statement cache, but does not provide a configurable wait‑timeout or acquisition timeout for obtaining a connection when the pool is full.

Uncertainty: Whether the IDE should expose a wait‑timeout option, rely on the underlying JDBC driver’s default timeout, or apply a hard‑coded safeguard remains unresolved, and observed hangs can differ across driver versions and NetBeans releases.

Should NetBeans add a user‑configurable wait‑timeout field to the pool editor?
Should it apply a default timeout when none is specified, or document that timeout behavior is driver‑dependent?
How should the IDE communicate pool‑exhaustion outcomes to users to avoid intermittent UI hangs?