spring-jms DefaultMessageListenerContainer when using retries cause comes as null in Dead Letter Queue using ActiveMQ

Hi Spring community,

I'm implementing retries with a DLQ in spring, I'm using the DefaultMessageListenerContainer but not the SimpleMessageListenerContainer, when the retries exceed the message in the DLQ looks like the following:

java.lang.Throwable: Delivery[2] exceeds redelivery policy imit:RedeliveryPolicy
{destination = queue://*,
collisionAvoidanceFactor = 0.15,
maximumRedeliveries = 1,
maximumRedeliveryDelay = -1,
initialRedeliveryDelay = 10000,
useCollisionAvoidance = false,
useExponentialBackOff = true,
backOffMultiplier = 5.0,
redeliveryDelay = 10000,
preDispatchCheck = true},
cause:null

the cause:null should be coming back with the exception that happened in the consumer but it doesn't, apparently in spring we are swallowing the exception (in the DefaultMessageListenerContainer) and ActiveMQ cannot remember the cause as per: http://activemq.2283324.n4.nabble.com/ActiveMQ-5-5-Not-able-to-get-the-DLQ-DELIVERY-FAILURE-CAUSE-PROPERTY-value-td3492931.html.

Start with DefaultMessageListenerContainer and compare its retry and exception handling with SimpleMessageListenerContainer. Reproduce the ActiveMQ DLQ flow using the stated redelivery policy, then verify that a consumer exception is preserved in the DLQ delivery-failure cause instead of appearing as cause:null.