[ 
https://issues.apache.org/jira/browse/CAMEL-25467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18126966#comment-18126966
 ] 

Claus Ibsen commented on CAMEL-25467:
-------------------------------------

Done in 
https://github.com/apache/camel/commit/d167b11e673837a71f6a116be7a7152952dabcc0 
(squashed together with CAMEL-25466):
* {{camel overview}} warns about three mistakes in the error handling, with the 
file and line. Agents get the warnings through {{camel_project_overview}}.
** A route that receives the failures of an error handler and uses it too. The 
warning advises an error handler of its own, such as a dead letter channel to a 
log; {{noErrorHandler}} with an onException ends in the fatal fallback, and a 
file consumer then reads the file again.
** A route with {{noErrorHandler}} that no route calls.
** An error handler that sends to an endpoint no route consumes.
* The Error handling section of the summary lists a route's own error handler, 
and what a global handler sends to that no route consumes.

The fail-well/error-handling example is changed so it no longer gets the 
warning: https://github.com/apache/camel-jbang-examples/pull/112

_Claude Code on behalf of Claus Ibsen_

> camel-jbang - findings about error handling (overview, monitor, agents)
> -----------------------------------------------------------------------
>
>                 Key: CAMEL-25467
>                 URL: https://issues.apache.org/jira/browse/CAMEL-25467
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-jbang
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 4.24.0
>
>
> Follow-up of CAMEL-25429. With the error paths known (route topology at 
> runtime, camel overview from the sources), some mistakes can be reported as 
> findings, with the source line, in camel overview, in the camel-jbang monitor 
> and to AI agents (the MCP tools):
> * an error route that uses the error handler that sends to it: a failure in 
> the error route comes back to it (e.g. a global dead letter channel to 
> direct:parked, and route parked uses that dead letter channel). Usually 
> wanted: noErrorHandler, or another handler, on the error route;
> * a route with noErrorHandler that no route calls: its failures have no 
> caller to go back to, and are lost;
> * an onException or a dead letter channel that sends to an endpoint no route 
> consumes (a direct or seda with no consumer).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to