camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CAMEL-667) Transactional Client - Uses DeadLetterChannel to much
Date Fri, 04 Jul 2008 19:53:00 GMT

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

Claus Ibsen resolved CAMEL-667.
-------------------------------

    Resolution: Fixed

Fixed with CAMEL-663 and that end-users should switch error handler to the transaction one
instead of the default.

Later as James write we can change the behavior in Camel 1.5 or 2.0.
Also the wiki documentation for the transactional client has been updated with this new error
handler.

> 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.


Mime
View raw message