[
https://issues.apache.org/activemq/browse/SMXCOMP-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen updated SMXCOMP-495:
------------------------------------
Attachment: SMXCOMP-495-detach.diff
Ron,
This error occurs because the underlying JBI MessageExchange for the Camel
Exchange has been answered when the Camel route is finishing up. I think the
best solution is to detach the Camel Exchange from the JBI MessageExchange once
the latter has been answered, to make sure the Camel Exchange can outlive the
JBI MessageExchange.
Attaching a quick patch now, I'll dig into things a bit more in the morning to
make sure there are no side-effects.
Gert
> smx-camel errorHandler does not forward CamelCaughtException message property
> to target JBI endpoint
> ----------------------------------------------------------------------------------------------------
>
> Key: SMXCOMP-495
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-495
> Project: ServiceMix Components
> Issue Type: Bug
> Components: servicemix-camel
> Affects Versions: servicemix-camel-2009.02
> Reporter: Ron Gavlin
> Assignee: Gert Vanthienen
> Fix For: 3.2.4, servicemix-camel-2009.02
>
> Attachments: camel_test_cleanup.patch, SMXCOMP-495-detach.diff,
> smxcomp-495.patch
>
>
> smx-camel errorHandler does not forward CamelCaughtException message property
> to target JBI endpoint. A unit test will be forthcoming.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
