Available from Camel 2.12
Camel supports a backlog debugger that is used for live debugging of message they are routed in Camel. The backlog debugger has additional functionality for easier debugging aimed at tooling, than the Debugger. The backlog debugger is exposed in JMX in the tracer node with the name
BacklogDebugger. The JMX API is defined in the
You can enable or disable the
BacklogDebugger dynamically, by calling
Whether to include the message body of file based messages. The overhead is that the file content has to be read from the file.
Whether to include the message body of stream based messages. If enabled then beware the stream may not be re-readable later. See more about Stream caching.
To limit the message body to a maximum size in the traced message.
Whether the debugger is enabled or not.
Whether currently in single step mode of a single Exchange.
To add a breakpoint at the given node.
To add a conditional breakpoint at the given node. The predicate is created from the language parameter.
To disable a breakpoint temporary.
To disable the debugger.
To dump the debugged messages from the give node id in XML format.
To active a breakpoint which has been temporary disabled.
To enable the debugger.
To get a set of all the nodes which has a breakpoint added.
Gets the total number of debugged messages.
To get a set of all the nodes which has suspended breakpoints e.g., an Exchange at the breakpoint which is suspended.
To reset the debugger counter.
To remove the breakpoint from the given node
To resume a suspend breakpoint, which will then continue routing the Exchange.
To resume all suspended breakpoints.
To step to next node when in single step mode.
To start single step mode from a suspended breakpoint at the given node. Then invoke
To update the message body on the suspended Exchange at the node.
To update/add the message header on the suspended Exchange at the node.
You would need to enable this using the JMX API.