Database Explorer connection pool exhaustion with no configurable pool parameters or diagnostic visibility

Goal

Diagnose intermittent connection pool exhaustion when NetBeans Database Explorer interacts with databases or application servers that enforce connection limits.

Constraints and uncertainty

The Data Sources UI exposes only URL, username, password, and driver class. HikariCP pool properties such as maximum pool size, idle timeout, minimum idle connections, and eviction policy are not configurable through the IDE. NetBeans 17 relies on HikariCP defaults (maximum pool size of 10), which may be unsuitable for environments with stricter connection caps. No built-in diagnostic surface—metrics, logs, or health endpoints—is provided to observe pool state, queue depth, or timeout events.

Questions

1. What programmatic or configuration approaches can expose HikariCP pool metrics from within the NetBeans runtime without modifying the IDE source?
2. Can a custom JDBC wrapper or JMX client be attached to the internal data source to observe real-time pool utilization and exhaustion events?
3. Are there documented extension points in the Database Explorer API that allow injecting pool configuration at data source registration time?