activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maxim Cherednik (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-6042) In ActiveMQMessageConsumer, always set rollback cause
Date Wed, 18 Nov 2015 12:29:11 GMT

    [ https://issues.apache.org/jira/browse/AMQ-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15010889#comment-15010889
] 

Maxim Cherednik commented on AMQ-6042:
--------------------------------------

Just one more thing: the version of the NMS client 1.6.2 is working fine

> In ActiveMQMessageConsumer, always set rollback cause
> -----------------------------------------------------
>
>                 Key: AMQ-6042
>                 URL: https://issues.apache.org/jira/browse/AMQ-6042
>             Project: ActiveMQ
>          Issue Type: Bug
>            Reporter: Martin Lichtin
>         Attachments: MessageListenerRedeliveryTest.java
>
>
> In ActiveMQMessageConsumer, 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.
> {code}
>     if (isAutoAcknowledgeBatch() || isAutoAcknowledgeEach() || session.isIndividualAcknowledge())
{
>         // schedual redelivery and possible dlq processing
>         md.setRollbackCause(e);
>         rollback();
>     } else {
>         // Transacted or Client ack: Deliver the next message.
>         afterMessageIsConsumed(md, false);
>     }
> {code}
> I'd suggest to move md.setRollbackCause(e); to before the if().



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

Mime
View raw message