You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Jonathan Anstey (JIRA)" <ji...@apache.org> on 2013/02/06 12:59:12 UTC

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

Jonathan Anstey created SMXCOMP-963:
---------------------------------------

             Summary: 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


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