Return-Path: Delivered-To: apmail-activemq-camel-user-archive@locus.apache.org Received: (qmail 4802 invoked from network); 30 Oct 2008 12:44:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 Oct 2008 12:44:37 -0000 Received: (qmail 27342 invoked by uid 500); 30 Oct 2008 12:44:42 -0000 Delivered-To: apmail-activemq-camel-user-archive@activemq.apache.org Received: (qmail 27318 invoked by uid 500); 30 Oct 2008 12:44:42 -0000 Mailing-List: contact camel-user-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: camel-user@activemq.apache.org Delivered-To: mailing list camel-user@activemq.apache.org Received: (qmail 27307 invoked by uid 99); 30 Oct 2008 12:44:42 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Oct 2008 05:44:42 -0700 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [195.69.129.177] (HELO exsmtp01.exserver.dk) (195.69.129.177) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Oct 2008 12:43:25 +0000 Received: from EXVS04.exserver.dk ([10.10.10.81]) by exsmtp01.exserver.dk with Microsoft SMTPSVC(6.0.3790.1830); Thu, 30 Oct 2008 13:40:58 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: Aggregator execution and timeout value Date: Thu, 30 Oct 2008 13:42:50 +0100 Message-ID: <4C1FB9C00D24A140906239533638C4D205CDB11B@EXVS04.exserver.dk> In-Reply-To: <20245908.post@talk.nabble.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Aggregator execution and timeout value Thread-Index: Ack6ivzNM2c6f8vPRxCi0hLoyLxQNQAAZlKg From: "Claus Ibsen" To: X-OriginalArrivalTime: 30 Oct 2008 12:40:58.0142 (UTC) FILETIME=[C20093E0:01C93A8C] X-Virus-Checked: Checked by ClamAV on apache.org Hi The timeout check is happening after your have added the exchange, so if = you take 5 seconds to add the exchange, then Camel will check the = timeout on next loop (BatchProcessor). So you should be home free, and = not lose any messages ;) See the source BatchProcessor. However the default batch timeout is *only* 1 sec. So you should be fast = to aggregate ;). I think most people must set a timeout value that fits = their use-case. Med venlig hilsen =20 Claus Ibsen ...................................... Silverbullet Skovsg=E5rdsv=E6nget 21 8362 H=F8rning Tlf. +45 2962 7576 Web: www.silverbullet.dk -----Original Message----- From: mta38 [mailto:mtaraud.ext@orange-ftgroup.com]=20 Sent: 30. oktober 2008 13:30 To: camel-user@activemq.apache.org Subject: Aggregator execution and timeout value Hi all, I have a question about aggregator behaviour and wish someone would help = me. Suppose my aggregationStrategy aggregate function is like that: Class MyaggregationStrategy implements AggregationStrategy { public Exchange aggregate(Exchange oldExchange, Exchange newExchange) { .. some longer process on oldExchange and newExchange... } ... } What happened if during aggregate function execution, because of timeout = (of the aggregator) the polling of the endpoint linked to the aggregator restart? Did in process modification on oldExchange and/or newExchange are lost?=20 Any help are welcome, Thanks in advance. mta38 --=20 View this message in context: = http://www.nabble.com/Aggregator-execution-and-timeout-value-tp20245908s2= 2882p20245908.html Sent from the Camel - Users mailing list archive at Nabble.com.