[
https://issues.apache.org/activemq/browse/CAMEL-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43948#action_43948
]
James Strachan commented on CAMEL-667:
--------------------------------------
BTW I've just added a TransactionalErrorHandlerBuilder...
https://issues.apache.org/activemq/browse/CAMEL-663
that never retries - but just rollsback the transaction which might be better
for transacational routes.
You can now use XML to specify this on the <camelContext> <route> or a
<pipeline> now
https://issues.apache.org/activemq/browse/CAMEL-662
https://issues.apache.org/activemq/browse/CAMEL-661
> Transactional Client - Uses DeadLetterChannel to much
> -----------------------------------------------------
>
> Key: CAMEL-667
> URL: https://issues.apache.org/activemq/browse/CAMEL-667
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-core, camel-spring
> Affects Versions: 1.4.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 1.4.0
>
>
> The new changes to the transactional client EIP pattern to let Camel support
> spring based TX does a trick to the DLC to set its max redeliveries to 1 if
> in transacted mode.
> This causes the normal DLC code to be executed and it will report that in
> case of failures that its being handled by its error handler, this is
> normally to move it to an error queue.
> This of course doesn't happen. The DLC should be short cutted to let the
> underlying system handling the redelivery without the DLC infecting it
> currently.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
