You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Maxim Cherednik (JIRA)" <ji...@apache.org> on 2015/10/26 13:49:27 UTC

[jira] [Created] (AMQNET-513) Exception message is not propagated in case of consumption failure

Maxim Cherednik created AMQNET-513:
--------------------------------------

             Summary: Exception message is not propagated in case of consumption failure
                 Key: AMQNET-513
                 URL: https://issues.apache.org/jira/browse/AMQNET-513
             Project: ActiveMQ .Net
          Issue Type: Bug
          Components: NMS
    Affects Versions: 1.7.0, 1.6.2
            Reporter: Maxim Cherednik
            Assignee: Jim Gomes


After moving from version 1.6.2 to 1.7 we lost some functionality we were relying on.
When we were failing to process message 6 times, it was moved to the Activemq.DLQ and the property dlqDeliveryFailureCause was filled with Exception message which was raised during the processing.
After version update - the exception message is not propagated. This message instead:
javax.jms.JMSException: Exceeded RedeliveryPolicy limit: 6

Maybe there are other way to track which client failed to process message and why(exception message) ?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)