Table of Contents
Debugging a route often involves solving one of two problems:
a message was improperly transformed
a message failed to reach its destination endpoint
Tracing one or more test messages through the route is the easiest way to discover the source of such problems.
The tooling's route tracing feature enables you to monitor the path a message takes through a route and see how the message is transformed as it passes from processor to processor.
Diagram view displays a graphical representation of the route, which enables you to see the path a message takes through it. For each processor in a route, it also displays the average processing time, in milliseconds, for all messages processed since route start-up and the number of messages processed since route start-up.
Messages view displays the messages processed by a JMS destination or route endpoint selected in the JMX Navigator tree. Selecting an individual message trace in Messages view displays the full details and content of the message in Properties view and highlights the correspoding node in Diagram view.
Tracing messages through a route involves the following steps: