camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: allowUseOriginalMessage="false" with useOriginalMessage="true" - new camel.breadcrumbId value
Date Mon, 30 Jan 2017 15:02:42 GMT
For your version of Camel you must yourself turn that allow on or off
depending on your use it or not.

>From Camel 2.18 onwards you will get an exception if you attempt to
access the original message and it was not allowed.

On Mon, Jan 30, 2017 at 3:58 PM, rsteppac2 <> wrote:
> Hello all,
> I stumbled across a misconfiguration in one of my routes where the context
> did not allow the use of the original message:
> <camelContext allowUseOriginalMessage="false">
> But by accident one of the routes had an onCompletion handler set to use the
> original message:
> <onCompletion useOriginalMessage="true">
> I don't think the onCompletion handler acutally got the original message.
> Unless the exchange property map is not a new instance and changes to the
> map during route processing are also reflected in the "original" message.
> But what happened was that a new camel.breadcrumbId was generated for the
> exchange in the onCompletion handler.
> Would that be a bug or a feature? If it is a feature, then why?
> I would have expected a warning or even an exception due to the
> configuration inconsistency.
> I am using Camel 2.16.3. I saw that
> changes the default setting
> of the Camel context for 2.18x. Has the behavior changed with 2.18? (I
> cannot test 2.18 due to AMQ incompatibilities.)
> Thanks!
> Ralf
> --
> View this message in context:
> Sent from the Camel - Users mailing list archive at

Claus Ibsen
----------------- @davsclaus
Camel in Action 2:

View raw message