[ 
https://issues.apache.org/jira/browse/CAMEL-26675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen resolved CAMEL-26675.
---------------------------------
    Resolution: Fixed

Merged to main in https://github.com/apache/camel/pull/29309

_Claude Code on behalf of davsclaus_

> camel-chaos - report accuracy: count an exchange once per route, start the 
> clock of startup rules at context start, cancel the expectation of a removed 
> rule, report a fault on the dead letter channel send
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-26675
>                 URL: https://issues.apache.org/jira/browse/CAMEL-26675
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-jbang
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 4.24.0
>
>
> * *Count once per exchange:* the route policy counts in {{onExchangeDone}}, 
> which runs on every pass through a route, so an exchange entering a 
> {{direct}} route 3 times counts 3 times (in completed/failed, the 
> expectations, and the {{until}} count of a {{route=}} corrupt rule). Count 
> once per exchange and route.
> * *Startup rules:* rules from {{camel.chaos.rules}} get their {{addedAt}} at 
> context initialization, so {{until=}}, {{within=}} and the lifecycle times 
> include the startup. Re-base them when the context has started.
> * *Never final:* an expectation of a removed or changed rule (or frozen by a 
> context restart) stays pending, so the report is never final again. It 
> becomes {{cancelled}}: not counted, not pending.
> * *Fresh start:* {{chaos-clear --reset}} also resets the report, the route 
> counts and the verdict (also in {{ChaosManager}} and the MCP clear tool).
> * *Dead letter channel:* a send to the dead letter channel is not matched by 
> {{endpoint=}} / {{component=}} rules unless the rule has {{at=dlq}}; a fault 
> there is reported as a lost message (today with 
> {{deadLetterHandleNewException}} it counts as handled, and the report says 
> lost 0).
> * The JSON report lists the versions of one rule id in order.
> Part of CAMEL-26667 (findings of the hands-on round of camel-chaos stage 1), 
> which has the scenarios.
> _Claude Code on behalf of Claus Ibsen_



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to