Claus Ibsen created CAMEL-26765:
-----------------------------------
Summary: camel-chaos - see through stub endpoints: suggestions for
stubbed remote endpoints, and kept consumers
Key: CAMEL-26765
URL: https://issues.apache.org/jira/browse/CAMEL-26765
Project: Camel
Issue Type: Improvement
Components: camel-jbang
Reporter: Claus Ibsen
Assignee: Claus Ibsen
Fix For: 4.24.0
With {{camel run --stub=remote --chaos}}, chaos does not see through the stubs
(found in the spike of CAMEL-26760, where an agent feeds stubbed consumers with
{{camel cmd send}}):
# {{chaos-suggest}} has nothing to suggest ("the routes call nothing remote,
and have no input from outside"): {{StubEndpoint.isRemote()}} is always false,
and the suggestions go by {{isRemote()}}.
# A route that reads {{kafka:refunds?breakOnFirstError=true}} through a stub
shows KEPT 0: {{ChaosConsumers.keepsFailed}} reads the option through the
configurer of the stub component, not Kafka's. And the stub consumer (a seda
queue) does not read a failed message again, as Kafka would. An exploration on
stubs would report "failed, not kept" for a route that keeps its messages.
Fix:
* A stub that stands in for another component (the stub component behind a
{{kafka:}} URI) counts as that component: remote when the component is remote
(from its JSON, which the factory finder finds when its JAR is on the
classpath, as camel run downloads it), and its kept options read from the URI.
* The report says per route that its consumer is a stub ({{stubbedConsumer}} in
the JSON), and that a kept message is not read again, so neither the report nor
an agent calls it lost.
Not in scope: making the stub consumer read a kept message again.
_Claude Code on behalf of Claus Ibsen_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
