Return-Path: X-Original-To: apmail-camel-users-archive@www.apache.org Delivered-To: apmail-camel-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id ABCFD101D1 for ; Wed, 10 Jul 2013 14:21:59 +0000 (UTC) Received: (qmail 44980 invoked by uid 500); 10 Jul 2013 14:21:59 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 44513 invoked by uid 500); 10 Jul 2013 14:21:58 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Received: (qmail 44496 invoked by uid 99); 10 Jul 2013 14:21:57 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Jul 2013 14:21:57 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of seanmckaybeck@gmail.com designates 74.125.83.42 as permitted sender) Received: from [74.125.83.42] (HELO mail-ee0-f42.google.com) (74.125.83.42) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Jul 2013 14:21:52 +0000 Received: by mail-ee0-f42.google.com with SMTP id c4so4983921eek.1 for ; Wed, 10 Jul 2013 07:21:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=51SiuyT8m/bRFj38HnyAiypzn2jasd64Zi/ftPsIiFU=; b=CzhbXklBQP4pjoPWQB5jA7y2YqoHtfbSnFwR7T46t+noLwnmnqKXc6tR37MyljTUm7 v3qIylZYSRCTpZ8CmATT5UpuCP186r7nBurE50E+2b58EL7iSm8NXdDgBYP3iupdW9kv AfT5z5P0/nIKIYrpn63vQmz5OCT4wgBU4A0o46tBK1mjjU6LIAo9QK++wfb2sl2FPxL5 He1W1kwwpf039CdOVj4k7D2CC0RSCFI6BmCpY+OGE+VP828LW2YvovUWltNN6fdH7y2r 2gbQvFSv5t0yzLe+Wql+wwoUzYKzV6DChjfR+m8gEboXTfjYrQx7rGV1zyoBkyvpS/l1 1JsA== MIME-Version: 1.0 X-Received: by 10.15.41.71 with SMTP id r47mr36143879eev.63.1373466091474; Wed, 10 Jul 2013 07:21:31 -0700 (PDT) Received: by 10.14.118.6 with HTTP; Wed, 10 Jul 2013 07:21:31 -0700 (PDT) In-Reply-To: References: Date: Wed, 10 Jul 2013 08:21:31 -0600 Message-ID: Subject: Re: Question on completionTimeout in AggregateDefinition From: Sean Beck To: users@camel.apache.org Content-Type: multipart/alternative; boundary=089e016816307e7e6204e128fe3c X-Virus-Checked: Checked by ClamAV on apache.org --089e016816307e7e6204e128fe3c Content-Type: text/plain; charset=ISO-8859-1 Awesome thanks. Timeout is what I am using and it seemed to be waiting for inactivity, which I wanted, but I wanted to make sure. On Tue, Jul 9, 2013 at 11:52 PM, Claus Ibsen wrote: > Hi > > There is 2 timer related options > - timeout > - interval > > The former is based on inactivity, and the latter is triggered in > fixed schedules after a given interval elapsed. > And the former is based on per correlated key, and the latter is > general and for all. > > See details at > http://camel.apache.org/aggregator2 > > > > On Wed, Jul 10, 2013 at 12:49 AM, Sean Beck > wrote: > > If i set the timeout for one minute in an aggregator will the timer > restart > > every time a new message comes over? Thanks > > > > -- > Claus Ibsen > ----------------- > Red Hat, Inc. > Email: cibsen@redhat.com > Twitter: davsclaus > Blog: http://davsclaus.com > Author of Camel in Action: http://www.manning.com/ibsen > --089e016816307e7e6204e128fe3c--