davsclaus opened a new pull request, #27518:
URL: https://github.com/apache/camel/pull/27518

   **The backlog tracer stamped route entry and exit with the exchange's 
creation time.**
   - It stamped the events of entering and leaving a route with 
`exchange.getClock().getCreated()`.
   - For the route the exchange started in, that is right.
   - For a route called later by the same exchange (direct, after a delay or 
redeliveries), the history went back in time: the called route's steps showed 
before the call that reached them.
   - Example, fail-well/error-handling in camel-jbang-examples, with 
redeliveries: from of checkout at 20.573, then unmarshal and to direct:charge 
at 22.633, then from of payment-provider at 20.573 again.
   
   **The fix:**
   - A route is entered at the time it is called. The route the exchange 
started in keeps the creation time.
   - The event of leaving a route carries the time the route was entered, as it 
already did for the first route. A reader adds the elapsed time to get the time 
it was left, as the camel-jbang tooling does, so older and newer readers agree.
   
   **throwException label:**
   - A throwException declared with `exceptionType` and `message`, as the YAML 
and XML DSLs declare it, was labelled `throwException[]` in traces and route 
history.
   - It is now labelled with the type and the message, e.g. 
`throwException[java.lang.IllegalStateException: card declined]`.
   
   **Tests:**
   - New `BacklogTracerCalledRouteTimestampTest`. It fails without the fix: the 
called route's entry was at the creation time, before a 200 ms delay.
   - The backlog tracer and debugger tests in camel-core and camel-management 
pass (50 in camel-management).
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   
   https://claude.ai/code/session_01STT6whBgK1AqsSsUKrnE8m


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to