Hi Ceposta,
Thanks for the input - it definitely shifted my position on which dead
letter queue to use.
Cheers,
Jesper
--
View this message in context:
http://camel.465427.n5.nabble.com/Transacted-processing-tp5741498p5741572.html
Sent from the Camel - Users mailing list archive at Nabble.com
They are two different levels of granulartiy.
ActiveMQ redelivery is at the JMS client level. Camel redelivery mechanics
is at the processor level. Same with the DLQ.
Example: you have a route like this:
form("activemq:queue:foo").log("Incoming message: ${body}").to("mock:end")
What this means:
Hi Claus,
Thanks for the quick reply...I have read the chapter, which covers
transactions well as you said. Still I am a bit unsure if there are any
advantages from using activemq`s retry plugin over camels...it looks like
camels retry supports roughly the same options. I guess given that my
prev
If you have a copy of Camel in Action book, then chapter 9 is a full
chapter about transactions, that goes deep.
On Mon, Oct 14, 2013 at 9:35 AM, Soelvar wrote:
> Hi all,
>
> I am currently in the progress of setting up camel for processing
> transactions. I am thinking to use transacted mode w
