apupier opened a new pull request, #29339: URL: https://github.com/apache/camel/pull/29339
# Description `CxfProducerTest.testInvokingAWrongServer` is still flaky after #29219 (30s `@Timeout` hit). The thread dump shows the test thread parked in `DefaultAsyncProcessorAwaitManager.await`: the exchange goes through the async `CxfProducer.process(Exchange, AsyncCallback)` path and waits for `CxfClientCallback.handleException` to call the Camel callback. When connecting to the unused port, that callback is sometimes never invoked, so the HTTP conduit connection/receive timeouts added in #29219 do not help. This PR sets `synchronous=true` on the "wrong server" endpoint of the test so the producer is wrapped in a `SynchronousDelegateProducer` and uses `CxfProducer.process(Exchange)`, which calls `Client.invoke` directly and returns (with the `IOException`) when the connection fails, without relying on an asynchronous callback. The test still verifies the `IOException` cause for the POJO, PAYLOAD and RAW data formats. Only test code is changed. The root cause (why the async callback is sometimes not invoked) is not investigated here. # Target - [x] I checked that the commit is targeting the correct branch (Camel 4 uses the `main` branch) # Tracking - [x] If this is a large change, bug fix, or code improvement, I checked there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for the change (usually before you start working on it). CAMEL-26600 # Apache Camel coding standards and style - [x] I checked that each commit in the pull request has a meaningful subject line and body. - [x] I have run `mvn clean install -DskipTests` locally from root folder and I have committed all auto-generated changes. _Claude Code-style AI disclosure: this PR was prepared by IBM Bob on behalf of @apupier._ -- 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]
