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

Posted to issues@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2015/11/30 20:15:11 UTC

[jira] [Resolved] (AMQCPP-588) Always set a rollback cause on exception thrown in onMessage

     [ https://issues.apache.org/jira/browse/AMQCPP-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish resolved AMQCPP-588.
---------------------------------
    Resolution: Fixed

> Always set a rollback cause on exception thrown in onMessage
> ------------------------------------------------------------
>
>                 Key: AMQCPP-588
>                 URL: https://issues.apache.org/jira/browse/AMQCPP-588
>             Project: ActiveMQ C++ Client
>          Issue Type: Improvement
>          Components: CMS Impl, Openwire
>    Affects Versions: 3.9.0
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>             Fix For: 3.9.1
>
>
> In ActiveMQMessageConsumerKernel, currently the rollback cause is only set for the case auto- or individual-acks. However, it should also be set for the other cases, so that in the rollback() method it can be picked up when creating the poison ack.  This ports the same fix as seen in AMQ-6042



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