shashank created CAMEL-26954:
--------------------------------
Summary: camel-core - BacklogDebugger: an exchange that is
single-stepped into a node replaces the exchange suspended there by a node
breakpoint
Key: CAMEL-26954
URL: https://issues.apache.org/jira/browse/CAMEL-26954
Project: Camel
Issue Type: Bug
Components: camel-core
Reporter: shashank
Assignee: shashank
Follow-up of CAMEL-26883, raised in the review of its PR (#29787).
{{DefaultBacklogDebugger}} keeps one suspended exchange per node
({{suspendedBreakpoints}} and {{suspendedBreakpointMessages}}, keyed by node
id). Since CAMEL-26883 a {{NodeBreakpoint}} registers with {{putIfAbsent}} and
removes only its own entry. {{StepBreakpoint.beforeProcess}} and its
{{doCompleted}} still use {{put}}.
Scenario: exchange E2 is suspended at node N by a node breakpoint, while
exchange E1 is single-stepped and steps into N (the debugger runs the node
breakpoints for exchanges that are not single-stepped, so both can be at N).
The step of E1 replaces the entry and the message of E2. A resume of N then
resumes E1 only, and E2 waits until the fallback timeout, as in the second
scenario of CAMEL-26883; the debugger no longer shows E2 as suspended.
Expected: a step does not replace another exchange suspended at the node. Which
way is a design choice (for example keep E2 and let the step of E1 wait for the
node, or key the suspended exchanges by node and exchange id); to agree on
before a fix. Developer tooling only (the debugger is not on in production).
Not reproduced with a test yet.
_Filed with Claude Code on behalf of allthingssecurity._
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)