Hi Thanks I have just had a look from the support case from RH. I can see that you do it a bit wrong, when you add onCompletion to the exchange, from the <onCompletion> - eg kinda like 2 times.
This causes the problem as when you do that the onCompletion, as your processor is called from on completion, you should just do your logic in the process method without adding a 2nd onCompletion. On Tue, Jul 7, 2015 at 11:41 AM, rwijngaa <rino.van.wijngaar...@gmail.com> wrote: > Hi Claus, > > The problem has to do with the onCompletion processor we use (and indeed, > maybe also with the osgi pax logging) In the logging i see one line with the > routeid and one line without the routeid. > > > > > I can reproduce it with the blueprint route, logging config and java class @ > fuse 6.2 included in the zip file. > mdc-logging-problem.zip > <http://camel.465427.n5.nabble.com/file/n5768939/mdc-logging-problem.zip> > > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/MDC-logging-does-not-work-with-camel-routeId-anymore-tp5768851p5768939.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
