You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/07/22 03:23:20 UTC
[jira] [Commented] (CAMEL-10172) BeanProducer unlike BeanProcessor
do not implement fully async protocol
[ https://issues.apache.org/jira/browse/CAMEL-10172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15388811#comment-15388811 ]
ASF GitHub Bot commented on CAMEL-10172:
----------------------------------------
GitHub user tivv opened a pull request:
https://github.com/apache/camel/pull/1085
CAMEL-10172: Make BeanProducer fully async
A patch and a test for CAMEL-10172
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tivv/camel bean-nonblocking
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/1085.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1085
----
commit 7d6e35b5f32f627b4e9537880666444f2c6ae7bb
Author: Vitalii Tymchyshyn <vi...@tym.im>
Date: 2016-07-22T03:21:04Z
CAMEL-10172: Make BeanProducer fully async
----
> BeanProducer unlike BeanProcessor do not implement fully async protocol
> -----------------------------------------------------------------------
>
> Key: CAMEL-10172
> URL: https://issues.apache.org/jira/browse/CAMEL-10172
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Reporter: Vitalii Tymchyshyn
>
> Currently BeanProducer converts any async call into a sync call.
> It leads to unnessesary locking & thread usage when using bean:* uris and routing to Async endpoints.
> The workaround is to use bean( * ) instead of to("bean:*") as this way BeanProducer is not used and BeanProcessor is fully async.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)