[CAMEL-4509] Header not set after dead letter queue handles unmarshal error

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.8.1
• Fix Version/s: 2.8.2, 2.9.0
• Component/s: camel-core

Environment

Java version: 1.6.0_11, vendor: Sun Microsystems Inc.
OS name: "windows xp", version: "5.1", arch: "x86", family: "windows"

• Estimated Complexity: Unknown
• Assignee: Claus Ibsen
• Reporter: Roy Truelove
• Created: 03/Oct/11 15:37
• Updated: 05/Oct/11 09:46
• Resolved: 05/Oct/11 09:46

Description

We have a route which unmarshals a soap msg into an object. On that route is a dead letter queue error handler. That DLQ sets headers on the message used later for error reporting.

If the error is thrown by the marshaller, the first header that we try to set is wiped out. The 2nd header is set with no problem. If an error is thrown by something other than the marshaller, the correct headers are set.

See attached project with failed test case (canSetHeadersOnBadXmlDeadLetter)