You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2015/08/13 00:00:46 UTC
[jira] [Commented] (AMQNET-506) Individual Ack Session with Message
Audit in play can detect false positive duplicates
[ https://issues.apache.org/jira/browse/AMQNET-506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14694254#comment-14694254 ]
ASF subversion and git services commented on AMQNET-506:
--------------------------------------------------------
Commit 1695615 from [~tabish121] in branch 'ActiveMQ/trunk'
[ https://svn.apache.org/r1695615 ]
Ensure the unacknowledged message are rolled back from the duplicate tracker on consumer close.
Fixes [AMQNET-AMQNET-506]. (See https://issues.apache.org/jira/browse/AMQNET-AMQNET-506)
> Individual Ack Session with Message Audit in play can detect false positive duplicates
> --------------------------------------------------------------------------------------
>
> Key: AMQNET-506
> URL: https://issues.apache.org/jira/browse/AMQNET-506
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: ActiveMQ
> Affects Versions: 1.6.5, 1.7.0
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Fix For: 1.7.1, 1.8.0
>
>
> When connected via a failover transport the connection enables its ConnectionAudit by default to filter duplicates. For messages consumed using a consumer created from a Session in Individual Acknowledgement mode the unacknowledged messages are not removed from the message audit when the consumer is closed. If a new consumer is opened on that same connection on the same destination the previously delivered messages get tagged as duplicates and are poisoned ack'd.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)