activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Serrano (Created) (JIRA)" <>
Subject [jira] [Created] (AMQ-3535) ActiveMQMessageConsumer auto ack of duplicates always sends a standard ack
Date Tue, 11 Oct 2011 12:41:11 GMT
ActiveMQMessageConsumer auto ack of duplicates always sends a standard ack

                 Key: AMQ-3535
             Project: ActiveMQ
          Issue Type: Bug
          Components: JMS client
    Affects Versions: 5.5.0
            Reporter: Martin Serrano
            Priority: Critical

When the ActiveMQMessageConsumer auto acks a duplicate, it always sends a standard ack.  This
occurs even when the session was opened in individual acknowledge mode.  This results in the
acknowledgments usually generating the "unmatched ack" message, causing the ack to be dropped.
 Since this is a duplicate, generally things are okay, but the spurious error message is troubling
and the inflight counts will be wrong from then on.

The following patch fixes the issue:

Index: src/org/apache/activemq/
--- src/org/apache/activemq/	(revision 46059)
+++ src/org/apache/activemq/	(working copy)
@@ -1257,7 +1257,8 @@
                             if (LOG.isDebugEnabled()) {
                                 LOG.debug(getConsumerId() + " ignoring (auto acking) duplicate:
" + md.getMessage());
-                            MessageAck ack = new MessageAck(md, MessageAck.STANDARD_ACK_TYPE,
+                            MessageAck ack = new MessageAck(md, (byte) session.acknowledgementMode,
                         } else {
                             if (LOG.isDebugEnabled()) {

I have also noticed that there are several places in ActiveMQMessageConsumer that allow potential
creation of acks that do not coincide with the session settings.  Perhaps ActiveMQSession.sendAck
should throw IllegalArgumentException if the ack type does not match the session?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message