Claus Ibsen created CAMEL-26679:
-----------------------------------
Summary: camel-chaos - new faults: error or corrupt after the
send, timeout, jittered delay, start offset, bursts, repeated lifecycle, more
corrupt modes
Key: CAMEL-26679
URL: https://issues.apache.org/jira/browse/CAMEL-26679
Project: Camel
Issue Type: Improvement
Components: camel-jbang
Reporter: Claus Ibsen
Assignee: Claus Ibsen
Fix For: 4.24.0
Faults that fit the current hooks ({{SendHook.afterSend}} can already change
the reply and set an exception), no API change:
* {{at=reply}}: {{error}} after the producer ran (the side effect happened,
then the send fails: the duplicate-payment test for retries), and {{corrupt}}
of the reply;
* a timeout: wait, then fail, in one rule ({{error after=5s}});
* a jittered delay from the seeded sequence ({{duration=100ms..2s}});
* a start offset ({{from=+30s}}): faults after warm-up;
* bursts ({{rate=burst:5s/30s}}): outage windows instead of an even rate;
* a flapping route ({{repeat=3 every=1m}} on {{stall}} / {{lifecycle}});
* corrupt modes {{empty}} and {{remove-header}}, and {{truncate}} for String
and byte[] bodies (skipped today).
A {{duplicate}} fault needs a "send again" result in the SendHook SPI and goes
to stage 2 (CAMEL-26607).
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)
