davsclaus opened a new pull request, #27999: URL: https://github.com/apache/camel/pull/27999
## Summary `ServerCertificateValidationTest.onlyClientsThatCanValidateTheServerCertificateConnect` fails on `main`: ``` mock://trustAll Received message count. Expected: <1> but was: <2> ``` CAMEL-25626 (#27908) and CAMEL-25645 (#27824) were merged 26 seconds apart on 2026-10-16, and neither PR build ran with the other change. Since CAMEL-25626, a consumer also delivers a null value with a Bad status. So the `trustAll` client, which connects before the test writes `Foo`, first receives the initial `DataValue[value=null, statusCode=Bad]` of `milo-server:myitem1`. The main build does not run the camel-milo tests, so it did not catch this. The failure shows up on every PR that touches camel-milo (for example #27910 and #27906). The consumer routes are now `autoStartup(false)`, and the test starts them after it writes the value, as `MonitorItemTest` does since CAMEL-25626. `Foo` is then the first notification of every client that connects, and the expectations do not change. Test-only change. ## Test plan - [x] `ServerCertificateValidationTest` fails on `main` (55ed20f14e90) and passes with this change (3 runs) - [x] Full `camel-milo` test suite: 74 run, 0 failures _Claude Code on behalf of Claus Ibsen_ 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
