camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antoine DESSAIGNE (JIRA)" <>
Subject [jira] [Commented] (CAMEL-7015) Allow timeout on the first Exchange for aggregator
Date Tue, 24 Jun 2014 06:32:24 GMT


Antoine DESSAIGNE commented on CAMEL-7015:

At first I though of adding an option telling whether or not the timeout is for the first
message received in this correlation group or for the last message.

But then I though, why not provide both timeouts ? You might want to 5 seconds after the last
exchange received but not more than 60 seconds after the first message. That way, if you have
an exchange every 4 seconds, you'll aggregate after one minute an not any longer.

Thus I named this parameter {{maxCompletionTimeout}} because I didn't wanted to rename the
{{completionTimeout}} parameter.

I'm not saying that it's the right way, or maybe it's not properly named. Don't hesitate to
ask if you want more insights about this patch.

> Allow timeout on the first Exchange for aggregator
> --------------------------------------------------
>                 Key: CAMEL-7015
>                 URL:
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-core, eip
>            Reporter: ChrisS
>            Assignee: Willem Jiang
>   Original Estimate: 168h
>  Remaining Estimate: 168h
> It would be nice to have a possibility of a timeout starting from the first Exchange
for messages having the same correlationExpression when using Aggregation.
> This scenario is currently not supported because "Its a bit tougher to implement as it
would require an improvement to TimeoutMap to support that as well."
> The full scenario is described in this thread:

This message was sent by Atlassian JIRA

View raw message