Affects Version/s: 2.1.0
Fix Version/s: 2.1.0
Similar Issues:Show 9 results
ECLIPSE-707 Add indicator that message tracing is enabled or not ECLIPSE-330 Message tracing - Improve cursor up/down and sort messages by default in the order they were received ECLIPSE-700 Enabling message tracing, causes diagram view to reset total counters ECLIPSE-1006 Camel context is always tracing messages ECLIPSE-703 Message tracing - Add pseudo stat and end rows to make it easier to see where a messages starts and ends ECLIPSE-326 Message tracing with Content Based Router, to highlight when/otherwise steps ECLIPSE-704 Processors View is empty when message tracing enabled ECLIPSE-325 Fuse Message Tracing vs Camel Tracing ECLIPSE-317 Trace messages seems not working
When you use message tracing, then you have a Messages View panel that shows the steps a message has taken.
And when you scroll up down in that list, its highlights how its being routed in the diagram view.
However the ordering in the Messages View seems a bit wrong.
The TracerMBean will report back the order as they happens in Camel, which is sorted using <uuid>. So the messages list should use that sorting as well.
See attached file which has 3 steps, for a given message
- to1 (route1)
- choice1 (route2)
- to3 (route2)
But the Messages View would list it as
Notice we can also correlate messages between routes send over transports using the breadcrumbId header. If this headers exists then its the "same" message. In this case it was routed over JMS.