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/06/29 08:31:00 UTC

[jira] [Updated] (CAMEL-23851) camel debug - breakpoint on first EIP incorrectly stops at route input

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

Claus Ibsen updated CAMEL-23851:
--------------------------------
    Component/s: camel-jbang

> camel debug - breakpoint on first EIP incorrectly stops at route input
> ----------------------------------------------------------------------
>
>                 Key: CAMEL-23851
>                 URL: https://issues.apache.org/jira/browse/CAMEL-23851
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-jbang
>    Affects Versions: 4.20.0
>            Reporter: Claus Ibsen
>            Priority: Minor
>             Fix For: 4.22.0
>
>
> When using {{camel debug}} with an explicit breakpoint on the first EIP in a route, the debugger stops at the route input (from/timer) instead of the specified EIP.
> For example:
> {code}
> camel debug route.yaml --breakpoint=setBody
> {code}
> If {{setBody}} is the first step after {{from}}, the breakpoint is placed on the {{from}} node instead of {{setBody}}.
> The cause is in {{DefaultChannel.backlogDebuggerSetupInitialBreakpoints()}}: when {{singleStepIncludeStartEnd}} is true and the matched node is the first output, the code replaces the breakpoint target with the route input. This logic was intended only for the special {{_all_routes_}} breakpoint but was incorrectly applied to all explicit breakpoints.



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