[
https://issues.apache.org/jira/browse/AMQ-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-3535.
-------------------------------
Resolution: Fixed
Fix Version/s: 5.6.0
Fix by AMQ-3568 from what I can tell. No test case on this issue to confirm it
solves all the reporters issues.
> ActiveMQMessageConsumer auto ack of duplicates always sends a standard ack
> --------------------------------------------------------------------------
>
> Key: AMQ-3535
> URL: https://issues.apache.org/jira/browse/AMQ-3535
> Project: ActiveMQ
> Issue Type: Bug
> Components: JMS client
> Affects Versions: 5.5.0
> Reporter: Martin Serrano
> Priority: Critical
> Fix For: 5.6.0
>
>
> 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 and dequeue counts will be wrong from then on.
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
