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 F0DEC200BD3 for ; Tue, 6 Dec 2016 16:22:55 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id EF939160B1B; Tue, 6 Dec 2016 15:22:55 +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 43A98160B0C for ; Tue, 6 Dec 2016 16:22:55 +0100 (CET) Received: (qmail 90676 invoked by uid 500); 6 Dec 2016 15:22:54 -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 90664 invoked by uid 99); 6 Dec 2016 15:22:54 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Dec 2016 15:22:54 +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 A1B131A07DE for ; Tue, 6 Dec 2016 15:22:53 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.313 X-Spam-Level: * X-Spam-Status: No, score=1.313 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, URIBL_BLOCKED=0.001, URI_HEX=1.313] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id jHvKSHjpKOlQ for ; Tue, 6 Dec 2016 15:22:49 +0000 (UTC) Received: from smtp125.ord1c.emailsrvr.com (smtp125.ord1c.emailsrvr.com [108.166.43.125]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 93ABD5F27E for ; Tue, 6 Dec 2016 15:22:49 +0000 (UTC) Received: from smtp8.relay.ord1c.emailsrvr.com (localhost [127.0.0.1]) by smtp8.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id A62F1A018C for ; Tue, 6 Dec 2016 10:22:42 -0500 (EST) Received: from smtp192.mex05.mlsrvr.com (unknown [184.106.31.85]) by smtp8.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTPS id 991D3A028D for ; Tue, 6 Dec 2016 10:22:42 -0500 (EST) X-Sender-Id: shuston@riverace.com Received: from smtp192.mex05.mlsrvr.com ([UNAVAILABLE]. [184.106.31.85]) (using TLSv1 with cipher AES256-SHA) by 0.0.0.0:25 (trex/5.7.12); Tue, 06 Dec 2016 10:22:42 -0500 Received: from ORD2MBX01D.mex05.mlsrvr.com ([fe80::75cf:4044:ec74:dde9]) by ORD2HUB15.mex05.mlsrvr.com ([fe80::be30:5bff:feee:c684%15]) with mapi id 14.03.0279.002; Tue, 6 Dec 2016 09:22:42 -0600 From: Steve Huston To: "users@camel.apache.org" Subject: RE: What to do with Null Body messages? Thread-Topic: What to do with Null Body messages? Thread-Index: AQHST9GjbSdNnGjjGU+J3ihiJSKg3KD7CW9g Date: Tue, 6 Dec 2016 15:22:42 +0000 Message-ID: <00BCD2BEF4977149A7C7303B4BAEBBE622D7DB78@ORD2MBX01D.mex05.mlsrvr.com> References: <1481036488638-5791139.post@n5.nabble.com> In-Reply-To: <1481036488638-5791139.post@n5.nabble.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [24.62.20.238] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 archived-at: Tue, 06 Dec 2016 15:22:56 -0000 You can set the ROUTE_STOP property to true. http://camel.apache.org/intercept.html has more info. > -----Original Message----- > From: sa_james [mailto:sa_reminder@hotmail.com] > Sent: Tuesday, December 06, 2016 10:01 AM > To: users@camel.apache.org > Subject: What to do with Null Body messages? >=20 > I have a processing Pipeline where I sometimes receive null-Body Message= s. > When I Forward the Messages to the next steps, there is an error. How do = I > get rid of the null-Body exchanges? I mean, they have to go somewhere. > Thx. >=20 >=20 >=20 > -- > View this message in context: http://camel.465427.n5.nabble.com/What-to- > do-with-Null-Body-messages-tp5791139.html > Sent from the Camel - Users mailing list archive at Nabble.com.