You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Ole Kristian Hofstad (Created) (JIRA)" <ji...@apache.org> on 2011/11/10 15:33:51 UTC
[jira] [Created] (CAMEL-4660) Hardcoded initial delay for
completionInterval in AggregatorService
Hardcoded initial delay for completionInterval in AggregatorService
-------------------------------------------------------------------
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
When setting the completionInterval on an aggregator, the first completion will be triggered after 1000ms. The reason is the hardcoded initial delay of 1000ms 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
[jira] [Updated] (CAMEL-4660) Hardcoded initial delay for
completionInterval in AggregatorService
Posted by "Ole Kristian Hofstad (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ole Kristian Hofstad updated CAMEL-4660:
----------------------------------------
Attachment: initialCompletionInterval.patch
Patch which sets the initial delay to the same value as the completionInterval
> Hardcoded initial delay for completionInterval in AggregatorService
> -------------------------------------------------------------------
>
> 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
>
>
> When setting the completionInterval on an aggregator, the first completion will be triggered after 1000ms. The reason is the hardcoded initial delay of 1000ms 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
[jira] [Updated] (CAMEL-4660) Hardcoded initial delay for
completionInterval in AggregatorProcessor
Posted by "Ole Kristian Hofstad (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ole Kristian Hofstad updated CAMEL-4660:
----------------------------------------
Description:
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.
was:
When setting the completionInterval on an aggregator, the first completion will be triggered after 1000ms. The reason is the hardcoded initial delay of 1000ms 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.
Summary: Hardcoded initial delay for completionInterval in AggregatorProcessor (was: Hardcoded initial delay for completionInterval in AggregatorService)
> Hardcoded initial delay for completionInterval in AggregatorProcessor
> ---------------------------------------------------------------------
>
> 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
>
>
> 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
[jira] [Resolved] (CAMEL-4660) Hardcoded initial delay for
completionInterval in AggregateProcessor
Posted by "Claus Ibsen (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-4660.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.9.0
2.8.3
Thanks for the patch
> 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
> Assignee: Claus Ibsen
> Priority: Minor
> Labels: Aggregation
> Fix For: 2.8.3, 2.9.0
>
> 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
[jira] [Updated] (CAMEL-4660) Hardcoded initial delay for
completionInterval in AggregateProcessor
Posted by "Ole Kristian Hofstad (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ole Kristian Hofstad updated CAMEL-4660:
----------------------------------------
Patch Info: Patch Available
Labels: Aggregation (was: aggregator)
> 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: Aggregation
> 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
[jira] [Updated] (CAMEL-4660) Hardcoded initial delay for
completionInterval in AggregateProcessor
Posted by "Ole Kristian Hofstad (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ole Kristian Hofstad updated CAMEL-4660:
----------------------------------------
Summary: Hardcoded initial delay for completionInterval in AggregateProcessor (was: Hardcoded initial delay for completionInterval in AggregatorProcessor)
> 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
>
>
> 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
[jira] [Assigned] (CAMEL-4660) Hardcoded initial delay for
completionInterval in AggregateProcessor
Posted by "Claus Ibsen (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen reassigned CAMEL-4660:
----------------------------------
Assignee: Claus Ibsen
> 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
> Assignee: Claus Ibsen
> Priority: Minor
> Labels: Aggregation
> 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
[jira] [Updated] (CAMEL-4660) Hardcoded initial delay for
completionInterval in AggregateProcessor
Posted by "Ole Kristian Hofstad (Updated) (JIRA)" <ji...@apache.org>.
[ 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