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

["Jonathan Anstey (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SMXCOMP-963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Anstey resolved SMXCOMP-963.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 2013.02

http://svn.apache.org/viewvc?rev=1442920&view=rev
                
> StaticRoutingSlip doesn't propagate errors to the caller endpoint when some endpoints in in the slip doesn't exist
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: SMXCOMP-963
>                 URL: https://issues.apache.org/jira/browse/SMXCOMP-963
>             Project: ServiceMix Components
>          Issue Type: Bug
>            Reporter: Jonathan Anstey
>            Assignee: Jonathan Anstey
>             Fix For: 2013.02
>
>
> 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... 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira