Return-Path: 
 <users-return-58521-apmail-camel-users-archive=camel.apache.org@camel.apache.org>
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 B1367180C2
	for <apmail-camel-users-archive@www.apache.org>;
 Tue, 22 Dec 2015 18:50:17 +0000 (UTC)
Received: (qmail 19194 invoked by uid 500); 22 Dec 2015 18:50:16 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 19142 invoked by uid 500); 22 Dec 2015 18:50:16 -0000
Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@camel.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@camel.apache.org>
List-Post: <mailto:users@camel.apache.org>
List-Id: <users.camel.apache.org>
Reply-To: users@camel.apache.org
Delivered-To: mailing list users@camel.apache.org
Received: (qmail 19126 invoked by uid 99); 22 Dec 2015 18:50:16 -0000
Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Dec 2015 18:50:16 +0000
Received: from localhost (localhost [127.0.0.1])
	by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org)
 with ESMTP id 3A5831A0325
	for <users@camel.apache.org>; Tue, 22 Dec 2015 18:50:16 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: 3.487
X-Spam-Level: ***
X-Spam-Status: No, score=3.487 tagged_above=-999 required=6.31
	tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2,
	SPF_SOFTFAIL=0.972, URIBL_BLOCKED=0.001, URI_HEX=1.313]
	autolearn=disabled
Received: from mx1-us-west.apache.org ([10.40.0.8])
	by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new,
 port 10024)
	with ESMTP id YyKwm8JL6gzk for <users@camel.apache.org>;
	Tue, 22 Dec 2015 18:50:07 +0000 (UTC)
Received: from mwork.nabble.com (mwork.nabble.com [162.253.133.43])
	by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with
 ESMTP id A467320FD3
	for <users@camel.apache.org>; Tue, 22 Dec 2015 18:50:07 +0000 (UTC)
Received: from msam.nabble.com (unknown [162.253.133.85])
	by mwork.nabble.com (Postfix) with ESMTP id 988D76BCC317
	for <users@camel.apache.org>; Tue, 22 Dec 2015 10:48:19 -0800 (PST)
Date: Tue, 22 Dec 2015 11:50:06 -0700 (MST)
From: vlad <vlad.oblamsky@gmail.com>
To: users@camel.apache.org
Message-ID: <1450810206024-5775368.post@n5.nabble.com>
In-Reply-To: 
 <CANHbvVsSWrB_0oOHAP=SF49eg3AijqA3OFw3ZVTrhDNLc-u8qw@mail.gmail.com>
References: <1450705852640-5775324.post@n5.nabble.com>
 <CANHbvVsSWrB_0oOHAP=SF49eg3AijqA3OFw3ZVTrhDNLc-u8qw@mail.gmail.com>
Subject: Re: Camel onException behavior with Splitter
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi Sundar,

I appreciate your answer, but I'm afraid it's not the case. 

According to the Apache Camel documentation, "handled" option only defines
if the exception should be propagated out of the current error handler. But
the error handler body still should be executed (in my example - the /<log
message="SOME MESSAGE"/>/ must be executed regardless of the handled value).

As for my example, I suspect that the Splitter's /shareUnitOfWork="true"/
somehow corrupts the exchange and it's not being properly handled in case of
some exception. If you remove this /shareUnitOfWork/ option then the SOME
MESSAGE is being printed regardless of the handled value.



--
View this message in context: http://camel.465427.n5.nabble.com/Camel-onException-behavior-with-Splitter-tp5775324p5775368.html
Sent from the Camel - Users mailing list archive at Nabble.com.