Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Tue, 24 Jun 2014 05:50:24 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12681431.1385504655545.34728.1403589024933@arcas>
In-Reply-To: <JIRA.12681431.1385504655545@arcas>
References: <JIRA.12681431.1385504655545@arcas>
Subject: [jira] [Commented] (CAMEL-7015) Allow timeout on the first Exchange
 for aggregator
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CAMEL-7015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14041728#comment-14041728 ] 

Claus Ibsen commented on CAMEL-7015:
------------------------------------

What is the idea with the maxCompletionTimeout? Will it not confuse end users that there is 2 timeouts now?

> Allow timeout on the first Exchange for aggregator
> --------------------------------------------------
>
>                 Key: CAMEL-7015
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7015
>             Project: Camel
>          Issue Type: New Feature
>            Reporter: ChrisS
>            Assignee: Willem Jiang
>              Labels: features
>   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: http://camel.465427.n5.nabble.com/A-simple-Aggregator-use-case-td5743633.html#a5743634


--
This message was sent by Atlassian JIRA
(v6.2#6252)