that property is only set in the ActiveMQMessageConsumer, when onMessage
throws an exception.
The value is then set as the poisonCause of a message ack.
In camel, the broker dlq processing is bypassed b/c the exceptions are
trapped by spring.
peek at
https://github.com/apache/activemq/blob/d54e0d6a
Hi,
Does anyone has seen the message property
DLQ_DELIVERY_FAILURE_CAUSE_PROPERTY set on the message moved to the DLQ when
using Camel in combination with a transacted?
So far, I have not...
I created some simple routes (one with Spring transaction manager, one with
ActiveMQ component), both wit
