Hi Camel community, I'm back with another issue, about Route-scoped errorHandler this time.
I have several Routes that have their own errorHandler. Each of these errorHandlers delegates Exceptions to a mutualized deadLetterChannel Route. The deadLetterChannel Route finally persists on disk the original Route's message (useOriginalMessage enabled) in order to be re-played later. The problem comes when I try to replay a File: I use a File Endpoint that read the file, convert its body to its original form, and then route the message to the original Route. But if this Route fails again, the deadLetterChannel is triggered with the wrong message (I see a GenericFile instead of the Type originally received by the Route). To sum this up, it seems the Route-scoped useOriginalMessage doesn't run as expected, as the message received by the target is always the initial message of the Exchange and not the one received by the route that failed (what I expect when I declare a Route-scoped errorHandler). You'll find as attachement a failing unit test that illustrates my problem: OriginalMessageDLCTest.java <http://camel.465427.n5.nabble.com/file/n5725682/OriginalMessageDLCTest.java> Any idea? Is it the expected behavior? Best regards, Nicolas -- View this message in context: http://camel.465427.n5.nabble.com/Route-scoped-errorHandler-and-useOriginalMessage-problem-tp5725682.html Sent from the Camel - Users mailing list archive at Nabble.com.
