camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ole Kristian Hofstad (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAMEL-4660) Hardcoded initial delay for completionInterval in AggregateProcessor
Date Thu, 10 Nov 2011 15:42:51 GMT

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

Ole Kristian Hofstad updated CAMEL-4660:
----------------------------------------

    Attachment: initialCompletionIntervalTest.patch

Added patch with test to reproduce the problem
                
> Hardcoded initial delay for completionInterval in AggregateProcessor
> --------------------------------------------------------------------
>
>                 Key: CAMEL-4660
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4660
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.8.2
>            Reporter: Ole Kristian Hofstad
>            Priority: Minor
>              Labels: aggregator
>         Attachments: initialCompletionInterval.patch, initialCompletionIntervalTest.patch
>
>
> When setting the completionInterval on an aggregator, the first completion will be triggered
after 1000ms. The reason is the hardcoded initial delay in AggregateProcessor.
> This behavior has not been documented and is not expected. The expected behavior is for
the first completion to be triggered after the given interval. The first completion would
then be triggered after completionInterval, the second after 2 * completionInterval, the third
after 3 * completionInterval and so on.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message