[
https://issues.apache.org/activemq/browse/CAMEL-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Purcell updated CAMEL-2059:
---------------------------------
Description:
When trying to add error logging to a transacted pipeline, I discovered the
following issues:
(1) onException/onCompletion do not work in a transacted route
(2) if the transacted tag is not the first element in the route, all the
endpoints above it will be silently ignored
(3) custom error handlers interact very awkwardly with transacted routes
(specifically, a non-transacted error handler will not work at all on a
transacted route)
I was able to solve my problem using doTry/doCatch; this may be a good
candidate for adding to the docs.
I suggest that, if the above issues are not corrected (especially 2+3, which
may not be route designs that it is desired to support), they should trigger
errors in the corresponding pipeline.
I have attached a tgz of examples showing problems (1) and (2) above, as well
as my successful route.
was:
When trying to add error logging to a transacted pipeline, I discovered the
following issues:
(1) onException/onCompletion do not work in a transacted route
(2) if the transacted tag is not the first element in the route, all the
endpoints above it will be silently ignored
(3) custom error handlers interact very awkwardly with transacted routes
I was able to solve my problem using doTry/doCatch; this may be a good
candidate for adding to the docs.
I have attached a tgz of examples showing problems (1) and (2) above, as well
as my successful route.
> Creating a transacted pipeline with custom error handling is difficult
> ----------------------------------------------------------------------
>
> Key: CAMEL-2059
> URL: https://issues.apache.org/activemq/browse/CAMEL-2059
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.0.0
> Reporter: Chris Purcell
> Fix For: Future
>
> Attachments: CamelTransactionsAndErrorHandling.tgz
>
>
> When trying to add error logging to a transacted pipeline, I discovered the
> following issues:
> (1) onException/onCompletion do not work in a transacted route
> (2) if the transacted tag is not the first element in the route, all the
> endpoints above it will be silently ignored
> (3) custom error handlers interact very awkwardly with transacted routes
> (specifically, a non-transacted error handler will not work at all on a
> transacted route)
> I was able to solve my problem using doTry/doCatch; this may be a good
> candidate for adding to the docs.
> I suggest that, if the above issues are not corrected (especially 2+3, which
> may not be route designs that it is desired to support), they should trigger
> errors in the corresponding pipeline.
> I have attached a tgz of examples showing problems (1) and (2) above, as well
> as my successful route.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
