BacklogDebugger
Available as of 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 org.apache.camel.api.management.mbean.ManagedBacklogDebuggerMBean
interface.
You can enable or disable the the BacklogDebugger
dynamically, by calling enableDebugger
or disableDebugger
methods.
...
Div |
---|
class | confluenceTableSmall |
---|
|
Option | Default | Description | enabled
| false |
---|
Whether the debugger is enabled or not. | bodyIncludeFiles
| true
| Whether to include the message body of file based messages. The overhead is that the file content has to be read from the file. | bodyIncludeStreams
| false
| 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. | bodyMaxChars
| 128kb
| To limit the message body to a maximum size in the traced message. Use 0 or negative value to use unlimited size. | enabled
| false
| Whether the debugger is enabled or not. | singleStepMode
| false
| Whether currently in single step mode of a single Exchange. |
|
...