Finally figured this one out. The issue wasn't the camel context (which is correct), but rather how the exchange message was being used in the processPayload method. Essentially I was altering the content of the Exchange.getIn() message with the updates instead of setting them in the Exchange.getOut() message. Once I made that change the process started working as expected!!!
Here's a link that explains this a bit and goes over the difference between getIn and getOut: https://cwiki.apache.org/confluence/display/CAMEL/Using+getIn+or+getOut+methods+on+Exchange https://cwiki.apache.org/confluence/display/CAMEL/Using+getIn+or+getOut+methods+on+Exchange -- View this message in context: http://camel.465427.n5.nabble.com/DeadLetterChannel-useOriginalMessage-Behaviour-tp4728373p4732018.html Sent from the Camel - Users mailing list archive at Nabble.com.
