PoolExhaustedException in norg connection pool

Connection Pool Exhaustion

The org.norg.pool.PoolExhaustedException occurs when concurrent requests exceed the defined maxPoolSize, indicating that no available connections remain in the pool for new operations.

Current configurations allow for the adjustment of maxPoolSize, idleTimeout, and evictionPolicy. However, the library lacks a mechanism for runtime resizing of the pool, requiring a restart to apply new limits during high-throughput spikes.

There is uncertainty regarding the behavior of connections that become idle during long-running transactions and how the idleTimeout interacts with these active but stalled sessions, which may contribute to intermittent exhaustion.

• Does norg support any undocumented method for dynamic pool scaling without a full application restart?
• How does the evictionPolicy handle connections that exceed the idleTimeout while tied to an open transaction?