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 28FD3200C63 for ; Thu, 11 May 2017 13:23:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 27851160BB2; Thu, 11 May 2017 11:23:08 +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 6E47C160BC7 for ; Thu, 11 May 2017 13:23:07 +0200 (CEST) Received: (qmail 80252 invoked by uid 500); 11 May 2017 11:23:06 -0000 Mailing-List: contact issues-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list issues@camel.apache.org Received: (qmail 80243 invoked by uid 99); 11 May 2017 11:23:06 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 May 2017 11:23:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 47D66180BB5 for ; Thu, 11 May 2017 11:23:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 0Ih5w96oo-Q1 for ; Thu, 11 May 2017 11:23:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 56AA65FCC1 for ; Thu, 11 May 2017 11:23:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id DB808E0D22 for ; Thu, 11 May 2017 11:23:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 275E821E10 for ; Thu, 11 May 2017 11:23:04 +0000 (UTC) Date: Thu, 11 May 2017 11:23:04 +0000 (UTC) From: "Claus Ibsen (JIRA)" To: issues@camel.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CAMEL-11229) Infinite recursion if exception happens inside exception handler MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 11 May 2017 11:23:08 -0000 [ https://issues.apache.org/jira/browse/CAMEL-11229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-11229: -------------------------------- Estimated Complexity: Advanced (was: Unknown) > Infinite recursion if exception happens inside exception handler > ---------------------------------------------------------------- > > Key: CAMEL-11229 > URL: https://issues.apache.org/jira/browse/CAMEL-11229 > Project: Camel > Issue Type: Bug > Components: camel-core > Affects Versions: 2.18.3 > Reporter: Christian Schneider > Assignee: Claus Ibsen > Fix For: 2.18.4, 2.19.1, 2.20.0 > > > Use an onException handler like this: > onException(Throwable.class).to("direct:handle_er"); > from("direct:handle_er")..throwException(new RuntimeException()); > If the main route throws an exception then this will create an infinite recursion of exceptions. > I would expect that camel handles the exception inside an onException handler differently. So the onException is not called again. -- This message was sent by Atlassian JIRA (v6.3.15#6346)