[
https://issues.apache.org/activemq/browse/CAMEL-2723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59383#action_59383
]
Claus Ibsen commented on CAMEL-2723:
------------------------------------
Also we should consider having an option on the endpoint {{async=true|false}}
which controls if a consumer/producer supports async should utilize it or not.
For example you may use transactions and want to send a req/reply over HTTP and
*not* utilize async so it all runs in the same thread so the transaction can be
fully supported.
> Asynchronous non blocking routing engine
> ----------------------------------------
>
> Key: CAMEL-2723
> URL: https://issues.apache.org/activemq/browse/CAMEL-2723
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 2.0.0, 2.1.0, 2.2.0, 2.3.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.4.0
>
> Attachments: CAMEL-2723-Channel.patch, CAMEL-2723-inprogress.patch
>
>
> The {{AsyncProcessor}} with the {{AsyncCallback}} logic (from Camel 1.x) is
> unfortunately our best solution for a fully asynchronous non blocking routing
> engine. The current logic its shortcoming when target under highly scalable
> environments, such as from a SMX container.
> The solution from 1.x is very invasive in the camel-core and requires a great
> deal of changes in various classes. But the pain is worth it to benefit the
> additional scalability it offers.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
