Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 24277200B92 for ; Wed, 28 Sep 2016 15:46:19 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 22C48160AC1; Wed, 28 Sep 2016 13:46:19 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 62564160AB4 for ; Wed, 28 Sep 2016 15:46:18 +0200 (CEST) Received: (qmail 13884 invoked by uid 500); 28 Sep 2016 13:46:05 -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 13805 invoked by uid 99); 28 Sep 2016 13:46:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Sep 2016 13:46:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 5372FCA840 for ; Wed, 28 Sep 2016 13:46:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.486 X-Spam-Level: *** X-Spam-Status: No, score=3.486 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972, URI_HEX=1.313] autolearn=disabled Received: from mx2-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id tjc7wKpDtvJA for ; Wed, 28 Sep 2016 13:46:02 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx2-lw-eu.apache.org (ASF Mail Server at mx2-lw-eu.apache.org) with ESMTP id C78A95FB6A for ; Wed, 28 Sep 2016 13:46:01 +0000 (UTC) Received: from static.162.255.23.22.macminivault.com (unknown [162.255.23.22]) by mbob.nabble.com (Postfix) with ESMTP id 94595323F7A6 for ; Wed, 28 Sep 2016 06:41:53 -0700 (PDT) Date: Wed, 28 Sep 2016 06:46:00 -0700 (MST) From: DariusX To: users@camel.apache.org Message-ID: <1475070360417-5788159.post@n5.nabble.com> In-Reply-To: <1475013518686-5788137.post@n5.nabble.com> References: <1474663524522-5787979.post@n5.nabble.com> <1474899697906-5788064.post@n5.nabble.com> <1475013518686-5788137.post@n5.nabble.com> Subject: Re: Loop should continue after exception caught. MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Wed, 28 Sep 2016 13:46:19 -0000 Do you find it is always breaking out of the loop or never breaking out? When I try the following code, the loop continues after being caught, unless I set the "CamelRouteStop" property, as shown below. from("direct:loopTest") .loop(simple("${body.size}")) .doTry() .process(new Processor1()) .to("log:LogPoint1") .doCatch(Exception.class) .setProperty("CamelRouteStop", constant(Boolean.TRUE)) .to("log:exception") .endDoTry(); -- View this message in context: http://camel.465427.n5.nabble.com/Loop-should-continue-after-exception-caught-tp5787979p5788159.html Sent from the Camel - Users mailing list archive at Nabble.com.