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 2013/09/23 12:25:13 UTC

[jira] [Resolved] (CAMEL-6775) Aggregate - Potential little optimization to send aggregated exchange to completion outside the lock

     [ https://issues.apache.org/jira/browse/CAMEL-6775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-6775.
--------------------------------

    Resolution: Fixed

Thanks for the test.
                
> Aggregate - Potential little optimization to send aggregated exchange to completion outside the lock
> ----------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-6775
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6775
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core, eip
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.13.0
>
>         Attachments: AggregatorLockingTest.java
>
>
> The aggregate eip needs to aggregate logic to operation in a lock. But if there is a completed aggregated exchange we can send that exchange to the downstream thread pool outside the lock.
> See nabble
> http://camel.465427.n5.nabble.com/Aggregator-lock-tp5739692.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira