[
https://issues.apache.org/jira/browse/CAMEL-9931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272464#comment-15272464
]
Claus Ibsen commented on CAMEL-9931:
------------------------------------
So it would be in the kafka completion something to create a runnable, which
you then submit to the thread pool. And in that runnable you call the camel
callback.done(false). And prior to that you set the result from kafka on the
exchange, so its been configured before continue routing.
And then we should allow to configure the thread pool on the camel kafka
component level, and override on the endpoint. So you can slice and dice. But
out of the box use a shared thread pool from the component.
> camel-kafka - Add support for async sending with callback
> ---------------------------------------------------------
>
> Key: CAMEL-9931
> URL: https://issues.apache.org/jira/browse/CAMEL-9931
> Project: Camel
> Issue Type: Improvement
> Components: camel-kafka
> Reporter: Claus Ibsen
> Fix For: Future
>
> Attachments: Producer Async V1.0.zip
>
>
> This requires us having a thread pool on the component that is used for
> processing the async replies when the kafka callback signals. Because we
> should not use its thread to continue routing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
