Martijn Visser created FLINK-41047:
--------------------------------------
Summary:
SqsSinkWriterTest.getNumRecordsOutErrorsCounterRecordsCorrectNumberOfFailures
gets a connection acquire timeout instead of Connection refused
Key: FLINK-41047
URL: https://issues.apache.org/jira/browse/FLINK-41047
Project: Flink
Issue Type: Bug
Components: Connectors / AWS
Affects Versions: aws-connector-6.1.0
Reporter: Martijn Visser
SqsSinkWriterTest.getNumRecordsOutErrorsCounterRecordsCorrectNumberOfFailures
failed in the nightly of 2026-10-17 (Flink 2.2-SNAPSHOT, JDK 21) after 62 s:
https://github.com/apache/flink-connector-aws/actions/runs/38985380518/job/117255514754
{code}
[ERROR]
org.apache.flink.connector.sqs.sink.SqsSinkWriterTest.getNumRecordsOutErrorsCounterRecordsCorrectNumberOfFailures
-- Time elapsed: 62.13 s <<< FAILURE!
java.lang.AssertionError:
Expecting throwable message:
"software.amazon.awssdk.core.exception.SdkClientException: Unable to execute
HTTP request: Acquire operation took longer than the configured maximum time.
[...] (SDK Attempt Count: 4)"
to contain:
"Unable to execute HTTP request: Connection refused: localhost/127.0.0.1:443"
but did not.
{code}
The test points the sink at https://localhost and expects the connection to be
refused. Here the SDK timed out acquiring a connection from its pool on all 4
attempts instead. It is the only red nightly of the last 30; the JDK 11 and 17
jobs of that run were cancelled by fail-fast.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
