[SMXCOMP-963] StaticRoutingSlip doesn't propagate errors to the caller endpoint when some endpoints in in the slip doesn't exist

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2013.02
• Assignee: Jonathan Anstey
• Reporter: Jonathan Anstey
• Created: 06/Feb/13 11:57
• Updated: 06/Feb/13 12:10
• Resolved: 06/Feb/13 12:10

Description

When the underlying channel (like the NMR) throws an Exception (like org.apache.servicemix.nmr.api.ServiceMixException: Could not dispatch exchange. No matching endpoints.) on send the StaticRoutingSlip just sets the error on the previous endpoint in the slip, not the original calling endpoint. What this means is that the flow stops (due to error) but there is no result returned back to the client. In the case of a Camel route, this would just hang the route...