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 queue and actually stay there. Before that, they seemed to be moved to he default ActiveMQ.DLQ because a response was excepted by the caller, but has never arrived.
So my question is, how would I actually use the custom defined error handler with the synchronous route using inOut()? I just want my route to be synchronous and I want to define my own deadletter queue, but those two things seem to be in conflict. Regards, Frankie -- View this message in context: http://activemq.2283324.n4.nabble.com/Problem-using-custom-defined-deadletter-queue-tp3135867p3135892.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
