From: sergiyvamz (@sergiyvamz) <noreply+sergiyvamz@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:52:48 +0000
Message-ID: <gh-aws-aws-advanced-jdbc-wrapper-2237-rc4621967419@github.com> (raw)
In-Reply-To: <gh-aws-aws-advanced-jdbc-wrapper-2237-rc4620804153@github.com>
References: <gh-aws-aws-advanced-jdbc-wrapper-2237@github.com>
<gh-aws-aws-advanced-jdbc-wrapper-2237-rc4620804153@github.com>
(on wrapper/src/main/java/software/amazon/jdbc/plugin/efm/v3/HostMonitorV3Impl.java)
Yes, done. Before, a runtime exception from the probe was caught by the outer loop and never counted, so the host could not be declared unhealthy while the driver kept throwing. It now counts as a failed probe and is logged at FINEST. The abort call catches Exception as well.