...
Camel provides the following context information available for MDC:
Camel 2.9.x or older
| Div |
|---|
| class | confluenceTableSmall |
|---|
|
Key | Description |
|---|
exchangeId | The exchange id | messageId | Camel |
|
| Wiki Markup |
|---|
{div:class=confluenceTableSmall}
|| Key || Description ||
| {{exchangeId}} | The exchange id |
| {{messageId}} | *Camel * id |
| {{correlationId}} | The correlation id of the exchange if id | correlationId | The correlation id of the exchange if it's |
EIP | transactionKey | The id of the transaction for transacted exchanges. Note the id is not unique, but its the id of the transaction template that marks the transaction boundary for the given transaction. Hence we decided to name the key transactionKey and not transactionID to point out this fact. | routeId | The id of the route, in which the exchange is currently being routed | breadcrumbId | Camel 2.8: An unique id used for tracking messages across transports. | camelContextId | Camel 2.8.3/2.9: |
|
Camel 2.10 onwards
| Div |
|---|
| class | confluenceTableSmall |
|---|
|
Key | Description |
|---|
camel.exchangeId | The exchange id | camel.messageId | The message id | camel.correlationId | The correlation id of the exchange if it's correlated. For example a sub message from the Splitter EIP | camel.transactionKey | The id of the transaction for transacted exchanges. Note the id is not unique, but its the id of the transaction template that marks the transaction boundary for the given transaction. Hence we decided to name the key transactionKey and not transactionID to point out this fact. | camel.routeId | The id of the route, in which the exchange is currently being routed | camel.breadcrumbId | An unique id used for tracking messages across transports. | camel.contextId | The camel context id used for tracking the message from different camel context. |
|
| Wiki Markup |
|---|
| {div:class=confluenceTableSmall}
|| Key || Description ||
| {{camel.exchangeId}} | The exchange id |
| {{camel.messageId}} | The message id |
| {{camel.correlationId}} | The correlation id of the exchange if it's correlated. For example a sub message from the [Splitter] EIP |
| {{camel.transactionKey}} | The id of the transaction for transacted exchanges. Note the id is not unique, but its the id of the transaction template that marks the transaction boundary for the given transaction. Hence we decided to name the key {{transactionKey}} and not {{transactionID}} to point out this fact. |
| {{camel.routeId}} | The id of the route, in which the exchange is currently being routed |
| {{camel.breadcrumbId}} | An unique id used for tracking messages across transports. |
| {{camel.contextId}} | The camel context id used for tracking the message from different camel context. |
{div} |
The keys are subject to change as we want to align and leverage MDC across other Apache products such as ActiveMQ, ServiceMix and Karaf.
...
