You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2026/10/14 07:56:00 UTC

[jira] [Resolved] (CAMEL-25467) camel-jbang - findings about error handling (overview, monitor, agents)

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

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

> 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)