Mark-
Another approach is to consume the message, add your headers and then produce
it back to the DLQ within a transaction on the same session. That will maintain
reliability, and allow you to enrich the message with some root cause
information.
-Matt
On Sep 11, 2014, at 7:08 AM, Marc Boorsh
Ah. Ok, that makes sense. Is that the standard way to handle exceptions
with JMS? Or is it vendor dependent?
Thanks
Marc
On Sep 11, 2014 6:38 AM, "Gary Tully" wrote:
> see
> https://github.com/apache/activemq/blob/d54e0d6ab590b6a6148a5e2629c45b95d3f40eb8/activemq-unit-tests/src/test/java/org/ap
see
https://github.com/apache/activemq/blob/d54e0d6ab590b6a6148a5e2629c45b95d3f40eb8/activemq-unit-tests/src/test/java/org/apache/activemq/MessageListenerRedeliveryTest.java#L317
an exception thrown from on message will force a rollback. There is an
internal try catch around the up call to onMess
Thats what I'm looking for to get the exception out of the failed message,
but how do I set it when I fail the message? There's no arguments to the
session.rollback() method and I don't see anything on the message its self.
Any help is greatly appreciated.
Thanks
Marc
On Wed, Sep 10, 2014 at 1
not really.
Peek at
https://github.com/apache/activemq/blob/d54e0d6ab590b6a6148a5e2629c45b95d3f40eb8/activemq-unit-tests/src/test/java/org/apache/activemq/MessageListenerRedeliveryTest.java#L285
for a unit test that covers the setting of the dlqDeliveryFailureCause
property on a message in the DL
I'm trying to add a stacktrace to a message if its been rolled back as a
property. Is this possible?
Thanks
Marc
