[
https://issues.apache.org/jira/browse/CAMEL-26747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-26747.
---------------------------------
Resolution: Fixed
Fixed by https://github.com/apache/camel/pull/29423 (52680d1d0fc3) on main, for
4.24.0.
_Claude Code on behalf of davsclaus_
> camel-jbang - chaos: a lost expectation counts parked messages, file
> endpoints get connection faults, and a cut countdown
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-26747
> URL: https://issues.apache.org/jira/browse/CAMEL-26747
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 4.24.0
>
>
> Three findings from writing the chaos example
> (apache/camel-jbang-examples#134):
> *1. A lost expectation counts the messages parked by the dead letter channel
> of the first route as lost*
> {{expect=orders->shipping:lost<=0}} counts every exchange completed in route
> {{orders}}, also one that its dead letter channel handled. An order that
> could not be charged and was parked by the DLC in {{orders}} never goes to
> {{shipping}}, by design, but the loss counted it: the verdict was FAIL with
> no message lost. Fix: the first route of a loss counts only the exchanges
> that completed without the error handler handling them. In the second route a
> handled exchange still counts as completed, as it arrived.
> *2. The advisor suggests connection refused and slow for a file endpoint*
> {{camel cmd chaos-suggest}} suggested "Refuses the connection" (a
> ConnectException) and "Is slow" for {{file:parked}}: a file endpoint is
> remote for Camel ({{Endpoint.isRemote()}}), but nothing connects. Fix: a new
> recipe "Fails to write" ({{write-error}}: {{error
> exception=java.io.IOException}}, as a full disk or a directory that cannot be
> written), suggested for a send to {{file:}} in place of the two.
> *3. The NOTE column of the chaos screen cuts "back in 903ms" to "903m"*
> At 150 columns the note of a stalled route read "suspended, back in 903m", as
> if 903 minutes. Fix: the countdowns in the note (back in, acts in, starts in,
> ends in, next burst in, burst left, next round in) are in whole seconds,
> rounded up: "back in 1s".
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
