[
https://issues.apache.org/jira/browse/CAMEL-4057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ben O'Day updated CAMEL-4057:
-----------------------------
Attachment: CAMEL-4057.patch
here is a proposed fix for this...just removing the Exchange.FAILURE_HANDLED
property from the exchange (when being continued) did the trick...I don't see
any side effects yet, but I'm still testing it...if anyone sees any issues with
this, let me know...thanks
> continued(true) doesn't work when is invoked for the second time in the Camel
> flow
> ----------------------------------------------------------------------------------
>
> Key: CAMEL-4057
> URL: https://issues.apache.org/jira/browse/CAMEL-4057
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.4.0, 2.7.2
> Environment: Apache Camel 2.4.0-fuse-00-00 and Apache Camel 2.7.2
> Reporter: Mateusz Nowakowski
> Assignee: Ben O'Day
> Labels: continued, exception, handler
> Fix For: 2.8.0
>
> Attachments: CAMEL-4057.patch, ContinuedTest.java
>
>
> When Camel flow contains error handling as continued(true), 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 interruped.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
