Hello,
I have been having few issues with my TransactionErrorHandler. It does not
seem to work as expected. More than like likely I am not configuring
properly.
I want to handle the retry and the DLC at the application level (Camel
level) and not at the Transport level (AMQ). It looks for retry and dlc my
TransactionErrorHandler configuration does not have any control at all.
* The retry count, retry intervel, the DLC channel all come from my default
broker configuration.
* I don't have the Exception that caused the retry.
I really need to handle the retry logic at the application level. I am bacth
processing 1000 records at a time. If I get an exception I want the message
to be routed to my DLC channel where another thread can pick it up break the
page size from 1000 records into 1 record at a time and do the rote again.
Can some one advise on the confiuguration? The following is the
configuration I have - whats wrong with it?
The config:
<property name=<b>"deadLetterUri"
value="activemq:queue:WH-IDK-work.DLQ" */>
and
<property name=<b>"maximumRedeliveries" value="4"* />
seem to have no effect at ll as ActiveMQ is fully in charge of retries and
DLC/
I do see this in the log.
It does mean that the redelivery is in fact orchestrated by AMQ (coarse
grained) and not by Camel (fine grained) as a "Read from the Queue" is
beginning of the JTA transaction.
I am not even sure why the re-delivery? I would like to fix it. By the time
the message ends in the AMQ DLC I have no idea! :(
Any help is really appreciated. Camel is great. *Everything I have learnt
and used is great! Just this pesky TransactionErrorHandling*
Thanks in advance!
Matt
-----
Thanks
Matt G. Madhavan
--
View this message in context:
http://camel.465427.n5.nabble.com/Hlep-Please-TransactionErroHandler-retry-DLC-issues-Stuck-tp5764363.html
Sent from the Camel - Users mailing list archive at Nabble.com.
