You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2021/03/09 14:01:00 UTC
[jira] [Commented] (CAMEL-16319) camel-core - Optimize consumer
done callback
[ https://issues.apache.org/jira/browse/CAMEL-16319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17298082#comment-17298082 ]
Claus Ibsen commented on CAMEL-16319:
-------------------------------------
This requires to go over each component that has consumers, and see if they do something special for their AsyncCallback or we can use a default one.
TODO: camel-timer *DONE*
> camel-core - Optimize consumer done callback
> --------------------------------------------
>
> Key: CAMEL-16319
> URL: https://issues.apache.org/jira/browse/CAMEL-16319
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 3.9.0
>
>
> Consumers that starts the routing by calling the first processor, have AsyncCallback as lambda which creates a new instance per message.
> If pooled we can for some consumers avoid this and reuse the lambda. But we need to find a way to make this transparent so the lambda can work in prototype vs pooled mode.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)