Closed lfernandez93 closed 11 months ago
thoughts?
We have observed the same behavior in our implementation of retries in spring. Any thoughts ?
Hello, I'm facing the same problem, is the correction planed in a future release ?
I just encountered the same problem today, did anyone find a solution to this?
Sorry this got overlooked. Can any of you share a small sample that reproduces the problem and that we can run ourselves? Without that, I am afraid we can't make much progress.
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.
Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.
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:
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.