Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Thu, 12 Apr 2012 08:57:23 +0000 (UTC)
From: "Radoslaw Szymanek (Reopened) (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: 
 <1088675228.16539.1334221044621.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1131284516.10811.1333529790894.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Reopened] (CAMEL-5139) Continued(Predicate) does not work
 when invoked the second time in the Camel flow.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CAMEL-5139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Radoslaw Szymanek reopened CAMEL-5139:
--------------------------------------

    Estimated Complexity: Advanced  (was: Novice)

I added an example of my route for which I hit the bug. Hopefully, it will be enough to reproduce the problem.
                
> Continued(Predicate) does not work when invoked the second time in the Camel flow.
> ----------------------------------------------------------------------------------
>
>                 Key: CAMEL-5139
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5139
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.9.1
>            Reporter: Radoslaw Szymanek
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.9.2, 2.10.0
>
>
> When Camel flow contains error handling as continued(Predicate), it is not invoked when the error occurs for the second time (even in different onException). What is more the exception is not handled even by global onException and Camel flow is interrupted. 
> It is similar issue to https://issues.apache.org/jira/browse/CAMEL-4057
> but not for continued(true) but continued(Predicate). 
> The same fix also fixes this problem. Simply adding 
> exchange.removeProperty(Exchange.FAILURE_HANDLED);
> just before returning true from the Predicate makes the second onException being called and the second time the exception is raised it can be continued again. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira