You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Gert Vanthienen (JIRA)" <ji...@apache.org> on 2009/03/27 15:57:42 UTC
[jira] Resolved: (SMXCOMP-489) When send to JBI fails from an async
Camel route, the Camel route will keep on waiting on the AsyncCallback
[ https://issues.apache.org/activemq/browse/SMXCOMP-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gert Vanthienen resolved SMXCOMP-489.
-------------------------------------
Resolution: Fixed
Fixed in http://svn.eu.apache.org/viewvc?view=rev&revision=759165
> When send to JBI fails from an async Camel route, the Camel route will keep on waiting on the AsyncCallback
> -----------------------------------------------------------------------------------------------------------
>
> Key: SMXCOMP-489
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-489
> Project: ServiceMix Components
> Issue Type: Bug
> Components: servicemix-camel
> Affects Versions: servicemix-camel-2009.01
> Reporter: Gert Vanthienen
> Assignee: Gert Vanthienen
> Fix For: servicemix-camel-2009.02
>
>
> When a Camel route that uses async Camel messaging sends a MessageExchange through JBI, it will use the same, asynchronous messaging style.
> If the JBI send() method fails (e.g. because the target endpoint is unknown), there will be no callback on the AsyncCallback effectively locking up the thread indefinitely.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.