Since we're on a major migration process of this website, some component documents here are out of sync right now. In the meantime you may want to look at the early version of the new website
We would very much like to receive any feedback on the new site, please join the discussion on the Camel user mailing list.

Message History

The Message History from the EIP patterns allows for analyzing and debugging the flow of messages in a loosely coupled system.

Attaching a Message History to the message will provide a list of all applications that the message passed through since its origination.

In Camel you can trace message flow using the Tracer, or access information using the Java API from UnitOfWork using the getTracedRouteNodes method.

When Camel sends a message to an endpoint that endpoint information is stored on the Exchange as a property with the key Exchange.TO_ENDPOINT.
This property contains the last known endpoint the Exchange was sent to (it will be overridden when sending to new endpoint). Alternatively you can trace messages being sent using interceptors or the Event Notifier.

Easier Message History

Available as of Camel 2.12

Message History is enabled by default from Camel 2.12. During routing Camel captures how the Exchange is routed, as a org.apache.camel.MessageHistory entity that is stored on the Exchange. On the org.apache.camel.MessageHistory there is information abut the route id, processor id, timestamp, and elapsed time it took to process the Exchange by the processor.

The information can be reached from Java code with:

List<MessageHistory> list = exchange.getProperty(Exchange.MESSAGE_HISTORY, List.class);

Enabling or disabling message history

The Message History can be enabled or disabled per CamelContext or per route. For example you can turn it off with


Or from XML DSL with

<camelContext messageHistory="false" ...>

You can also do this per route. Then a route level configuration overrides the CamelContext level configuration.

Route stack-trace in exceptions logged by error handler

If Message History is enabled, then Camel will leverage this information, when the Error Handler logs exhausted exceptions. Then in addition to the caused exception with its stacktrace, you can see the message history; you may think this as a "route stacktrace". And example is provided below:

2013-05-31 14:41:28,084 [ - seda://start] ERROR DefaultErrorHandler            - Failed delivery for (MessageId: ID-davsclaus-air-lan-55446-1370004087263-0-1 on ExchangeId: ID-davsclaus-air-lan-55446-1370004087263-0-3). Exhausted after delivery attempt: 1 caught: java.lang.IllegalArgumentException: Forced to dump message history

Message History
RouteId              ProcessorId          Processor                                                                        Elapsed (ms)
[route1            ] [to1               ] [log:foo                                                                       ] [         6]
[route1            ] [to2               ] [direct:bar                                                                    ] [       102]
[route2            ] [to5               ] [log:bar                                                                       ] [         1]
[route2            ] [delay2            ] [delay[{100}]                                                                  ] [       100]
[route2            ] [to6               ] [mock:bar                                                                      ] [         0]
[route1            ] [delay1            ] [delay[{300}]                                                                  ] [       303]
[route1            ] [to3               ] [log:baz                                                                       ] [         0]
[route1            ] [process1          ] [org.apache.camel.processor.MessageHistoryDumpRoutingTest$1$1@6a53f9d8         ] [         2]

java.lang.IllegalArgumentException: Forced to dump message history
	at org.apache.camel.processor.MessageHistoryDumpRoutingTest$1$1.process(
	at org.apache.camel.processor.DelegateSyncProcessor.process(
	at org.apache.camel.processor.RedeliveryErrorHandler.process(
	at org.apache.camel.processor.CamelInternalProcessor.process(
	at org.apache.camel.processor.Pipeline.process(
	at org.apache.camel.processor.Pipeline.process(
	at org.apache.camel.processor.DelayProcessorSupport.process(
	at org.apache.camel.processor.RedeliveryErrorHandler.process(
	at org.apache.camel.processor.CamelInternalProcessor.process(
	at org.apache.camel.processor.Pipeline.process(
	at org.apache.camel.processor.Pipeline.process(
	at org.apache.camel.processor.CamelInternalProcessor.process(
	at org.apache.camel.component.seda.SedaConsumer.sendToConsumers(
	at org.apache.camel.component.seda.SedaConsumer.doRun(
	at java.util.concurrent.ThreadPoolExecutor.runWorker(
	at java.util.concurrent.ThreadPoolExecutor$

You can turn off logging message history from the Error Handler using


From Camel 2.17 onwards the Error Handler do not log the message body/header details anymore (to avoid logging sensitive message body details). You can turn on the old behavior.



Using This Pattern

If you would like to use this EIP Pattern then please read the Getting Started, you may also find the Architecture useful particularly the description of Endpoint and URIs. Then you could try out some of the Examples first before trying this pattern out.

© 2004-2015 The Apache Software Foundation.
Apache Camel, Camel, Apache, the Apache feather logo, and the Apache Camel project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.
Graphic Design By Hiram