activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (AMQCPP-588) Always set a rollback cause on exception thrown in onMessage
Date Mon, 30 Nov 2015 19:14:11 GMT


ASF subversion and git services commented on AMQCPP-588:

Commit f0ecb22d8972f4849819a588e2a707192b39e8eb in activemq-cpp's branch refs/heads/3.9.x
from [~tabish121]
[;h=f0ecb22 ]

Fix NPE error.
Update onMessage processing to always incluide the error cause exception
so that the poison cause in DLQ contains the original error message.
(cherry picked from commit ce523a140112d4d654e8ae660893e09bf9ffd7c3)

> Always set a rollback cause on exception thrown in onMessage
> ------------------------------------------------------------
>                 Key: AMQCPP-588
>                 URL:
>             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

View raw message