[jira] [Resolved] (SMXCOMP-964) Camel doesn't return error while invoking jbi endpoint which doesn't exist, setting up a infinite loop on retry.

["Willem Jiang (JIRA)" <ji...@apache.org>]

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

Willem Jiang resolved SMXCOMP-964.
----------------------------------

    Resolution: Fixed
      Assignee: Willem Jiang

Applied the patch into trunk.
                
> Camel doesn't return error while invoking jbi endpoint which doesn't exist, setting up a infinite loop on retry.
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: SMXCOMP-964
>                 URL: https://issues.apache.org/jira/browse/SMXCOMP-964
>             Project: ServiceMix Components
>          Issue Type: Bug
>            Reporter: Willem Jiang
>            Assignee: Willem Jiang
>
> If camel route the message to the no exit endpoint, the camel route will keep on sending the message on the same endpoint and get the OOM error.
> After digging the issue for a while, I found the old javax.jbi.serviceName property is set on Exchange message when the CamelConsumerEndpoint send the message out. That cause the CamelConsumerEndpoint keep send the message to same old jbi endpoint again and again.
> As the user doesn't leverage the javax.jbi.* property to change to routing the jbi enpdoint dynamically (Camel provides the jbi:xxx uri for this kind of requirement). We could a new header filter strategy by default to avoid copying the javax.jbi.* header across the camel exchange and servicemix exchange to avoid this kind of issue.

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