JiriOndrusek opened a new issue, #9529:
URL: https://github.com/apache/camel-quarkus/issues/9529

   ### Problem
   `TlsRegistryMutualTlsTest.callWithoutClientCertificateIsRejected(String)[1]` 
(`integration-tests/tls-registry`, test added in e76ea030b8) fails 
intermittently with:
   
   ```
   java.net.SocketException: Broken pipe
   TlsRegistryMutualTlsTest.callWithoutClientCertificateIsRejected:82 1 
expectation failed.
   ```
   
   Seen in the `camel-main` CI run 
https://github.com/apache/camel-quarkus/actions/runs/44485007925 (Native Tests 
- group-10, JVM test of the module, 1 failure out of 21 tests). The same test 
passed on the other runs, and locally it failed in 1 of 5 runs with the same 
`Broken pipe`.
   
   The Camel route log shows the Apache HttpClient retry before the failure:
   
   ```
   recoverable I/O exception (java.net.SocketException) caught when sending 
request to https://localhost:8543; request will be automatically re-executed 
(exec count 2)
   Failed delivery for ... at route1. Exhausted after delivery attempt: 1 
caught: java.net.SocketException: Broken pipe
   ```
   
   ### Likely cause
   With TLS 1.3 the client finishes its handshake before the server has checked 
the (missing) client certificate. The server then rejects the connection with 
an alert, while the client may already be writing the request. Depending on 
timing the client sees a TLS alert (what the test expects) or `Broken pipe`.
   
   ### Suggested fix
   Make the test independent of that timing, either:
   - pin the test server to TLS 1.2 (the rejection then happens in the 
handshake), or
   - accept the socket-level failure (`SocketException`) as well as the TLS 
alert as "rejected".
   
   _Generated with [Claude Code](https://claude.com/claude-code) on behalf of 
@JiriOndrusek_


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to