From: aaron-congo (@aaron-congo) <noreply+aaron-congo@github.com>
To: aws/aws-advanced-jdbc-wrapper <noreply+aws-aws-advanced-jdbc-wrapper@github.com>
Subject: Re: [aws/aws-advanced-jdbc-wrapper] PR #2237: feat: add efm3 host monitoring plugin with per-connection registration
Date: Wed, 18 Nov 2026 22:04:13 +0000
Message-ID: <gh-aws-aws-advanced-jdbc-wrapper-2237-rc4621482155@github.com> (raw)
In-Reply-To: <gh-aws-aws-advanced-jdbc-wrapper-2237@github.com>
References: <gh-aws-aws-advanced-jdbc-wrapper-2237@github.com>
(on wrapper/src/main/java/software/amazon/jdbc/plugin/efm/v3/HostMonitorV3Impl.java)
`sweepSlots` unregisters any slot that has been idle longer than `monitorDisposalTime`. As a result, `abortIdleConnectionsOnFailure` skips connections that have been idle for more than 10 minutes by default, and long-idle pooled connections are probably the main thing that option is for.
Example: `abortIdleConnectionsOnFailure=true` with the default `monitorDisposalTime=600000`. Pooled connections that have been idle for 15 minutes are no longer registered. When the host fails, only the recently used connections are aborted. The rest stay in the pool and fail on their next checkout. The docs say idle connections to the host are aborted, with no time limit.
Should idle slots skip eviction when `abortIdleConnections` is set, and rely on the weak reference being cleared to remove them?