davsclaus opened a new pull request, #29423: URL: https://github.com/apache/camel/pull/29423
[CAMEL-26747](https://issues.apache.org/jira/browse/CAMEL-26747): three findings from writing the chaos example (apache/camel-jbang-examples#134). **1. A lost expectation counted the messages parked by the dead letter channel of the first route as lost.** `expect=orders->shipping:lost<=0` counted every exchange completed in `orders`, also one its dead letter channel handled. Such an order never goes to `shipping`, by design, yet the verdict was FAIL. Now the first route of a loss counts only the exchanges that completed without the error handler handling them (`ChaosManager.record`). In the second route a handled exchange still counts as completed, as it arrived. The new test `theMessagesParkedByTheDeadLetterChannelAreNotLost` fails without the fix. **2. The advisor suggested "Refuses the connection" and "Is slow" for a `file:` send.** A file endpoint is remote for Camel (`Endpoint.isRemote()`), but nothing connects. A new recipe, "Fails to write" (`write-error`: `error exception=java.io.IOException`, as a full disk or a directory that cannot be written), with its guide, is suggested for `file:` in place of the two. `chaos-model.json` and its catalog copy are regenerated. **3. The NOTE column of the chaos screen cut "back in 903ms" to "903m"**, which reads as 903 minutes. The countdowns in the note are now whole seconds, rounded up (`ChaosTab.countdown`): "back in 1s". Docs: `chaos.adoc` (and its catalog copy) says how a loss treats handled exchanges. Tests: camel-chaos (all), camel-jbang-plugin-tui `Chaos*Test`. _Claude Code on behalf of Claus Ibsen_ -- 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]
