Can you reproduce this in a standalone debugging environment (not production)? Maybe not right away, but reasonably? Because you could start the broker with the debugging port opened and attach Eclipse (or your favorite debugger) to the broker process, then set a breakpoint on the line in Queue.java that outputs the log line you've copied above (you'll want a conditional breakpoint with a condition that the destination is queue://ActiveMQ.DLQ so you don't stop there on every message). Then when you hit the breakpoint, you can hopefully walk up the stack trace to figure out what caused the issue. (In Eclipse, the Drop To Frame button will let you restart whatever method you've currently selected in the stack trace, so you can walk through the code again and see how you got to the log line.) I expect you'll find that the broker is being told by the ActiveMQ code in the client that the message failed delivery, so then you'll probably want to do the same kind of debugging exercise on the client...
Also, have you enabled debug logging for both ActiveMQ and Camel in the client? If not, I'd do that before I went to the debugger. On Wed, Jan 14, 2015 at 7:24 AM, gijsbert802 <vandenbr...@zorgdomein.nl> wrote: > I tried that, but I only see that a message is being sent to my "incoming" > queue and then some time later it is sent to the DLQ. There are no other > references to that message-id in the logs. > > Something like this: > > 2015-01-14 14:18:39,473 DEBUG o.a.activemq.broker.region.Queue - localhost > Message ID:ZD68105205-2.local-54923-1421245093739-1:1:10:1:1 sent to > queue://incoming > ... > 2015-01-14 14:19:10,824 DEBUG o.a.activemq.broker.region.Queue - localhost > Message ID:ZD68105205-2.local-54923-1421245093739-1:1:10:1:1 sent to > queue://ActiveMQ.DLQ > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Message-is-moved-to-DLQ-without-clear-cause-tp4689889p4689899.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
