You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2011/03/22 14:36:05 UTC
[jira] [Created] (AMQ-3236) In the case of DLQ processing due to an
exception from onMessage, provide the exception string as a message
property
In the case of DLQ processing due to an exception from onMessage, provide the exception string as a message property
---------------------------------------------------------------------------------------------------------------------
Key: AMQ-3236
URL: https://issues.apache.org/jira/browse/AMQ-3236
Project: ActiveMQ
Issue Type: New Feature
Components: Broker
Affects Versions: 5.4.2
Reporter: Gary Tully
Assignee: Gary Tully
Fix For: 5.5.0
When an application throws an exception from on message, redelivery kicks in through session rollback. If the policy dictates that the message should be sent to the DLQ, the exception cause is lost.
The enhancement would pipe the exception with the internal poison ack such that it can be included as a message property in the message in the DLQ.
Some context in the answer http://stackoverflow.com/questions/5069733/preservation-of-exception-cause-when-redelivering-failed-activemq-jms-messages-pr/5109361#5109361
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (AMQ-3236) In the case of DLQ processing due to
an exception from onMessage, provide the exception string as a message
property
Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully resolved AMQ-3236.
-----------------------------
Resolution: Fixed
A property with the cause is now supported. For a message on the DLQ where the redelivery failure was a result of an application exception (exception from MessageListener.onMessage()), the cause is visible via:{code}String cause = message.getStringProperty(ActiveMQMessage.DLQ_DELIVERY_FAILURE_CAUSE_PROPERTY);{code}
implemented in rev: http://svn.apache.org/viewvc?rev=1084175&view=rev
> In the case of DLQ processing due to an exception from onMessage, provide the exception string as a message property
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-3236
> URL: https://issues.apache.org/jira/browse/AMQ-3236
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker
> Affects Versions: 5.4.2
> Reporter: Gary Tully
> Assignee: Gary Tully
> Labels: DLQ, Exception, Redelivery
> Fix For: 5.5.0
>
>
> When an application throws an exception from on message, redelivery kicks in through session rollback. If the policy dictates that the message should be sent to the DLQ, the exception cause is lost.
> The enhancement would pipe the exception with the internal poison ack such that it can be included as a message property in the message in the DLQ.
> Some context in the answer http://stackoverflow.com/questions/5069733/preservation-of-exception-cause-when-redelivering-failed-activemq-jms-messages-pr/5109361#5109361
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira