Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Tue, 29 Sep 2015 06:26:04 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12853822.1439209464000.99710.1443507964548@Atlassian.JIRA>
In-Reply-To: <JIRA.12853822.1439209464000@Atlassian.JIRA>
References: <JIRA.12853822.1439209464000@Atlassian.JIRA>
 <JIRA.12853822.1439209464071@arcas>
Subject: [jira] [Updated] (CAMEL-9069) Add processor to immediately handle
 exception while in retry loop
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/CAMEL-9069?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-9069:
-------------------------------
    Priority: Major  (was: Trivial)

> Add processor to immediately handle exception while in retry loop
> -----------------------------------------------------------------
>
>                 Key: CAMEL-9069
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9069
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Kevin Telford
>             Fix For: 2.17.0
>
>
> We have a recipientList of http4 endpoints.  Occasionally an endpoint won=
't be available, and will return an exception (whether a ConnectException, =
or any other ex and a status code of >=3D400).  To handle these errors we c=
an use a defaultErrorHandler or leverage onException, and setup redelivery.=
 What we then would like to do is some custom error handling on each occurr=
ence of an exception.
> Both the defaultErrorHandler and onException support .onRedelivery().  Wh=
ile this is nice, when a retry delay grows large enough the lag between the=
 exception and the .onRedelivery() call really begins to grow and so our cu=
stom error handling isn't as much =E2=80=9Con error=E2=80=9D as it is =E2=
=80=9Con error and after a wait=E2=80=9D.
> onException also supports a .process() call, however this only occurs onc=
e all redeliveries have failed.
> What would be ideal would be an additional .onExceptionOccur(Processor pr=
ocessor) method (or some such name) that allows for immediate processing up=
on an exception, even if its being handled within a retry loop.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)