Hi,
Thank you for your reply! I managed to solve the problem by simply upgrading
to the new version of Camel (2.5) which eliminated all of the symptoms
described above.
Regards,
Frankie
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Problem-using-custom-defined-deadlett
Hi,
you can find more options on ActiveMQ DLQ settings here
http://activemq.apache.org/message-redelivery-and-dlq-handling.html
Maybe you can just rename the default deadletter queue to the one you
want to use. As for you other question, you should try the camel user
list.
Cheers
--
Dejan Bosana
Hi,
I've got some new findings regarding the problem above. I manage to figure
out that the cause to the problem is the .inOut() at the beginning of the
"direct:start" route. If I comment out the .inOut(), than, upon exception
and 3 retries, the messages end up in my custom defined DEADLETTER que
