Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <16966487.10921290540205443.JavaMail.jira@thor>
Date: Tue, 23 Nov 2010 14:23:25 -0500 (EST)
From: "Gary Tully (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Resolved: (AMQ-2985) Missing messages in durable
 subscription with selector and KahaDB
In-Reply-To: <21149500.59241287393760357.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/activemq/browse/AMQ-2985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully resolved AMQ-2985.
-----------------------------

    Resolution: Fixed

r1038276 - ackLocations are created on message send, such that subs can ack at their will, due to unmatched or out of order due to priority. subscription acks hold priority along with the last ack, such that the order cursors can be correctly chosen after a restart or reset. This ensures that duplicates are not dispatched as the current position is now ack aware rather than shared across priority.
This brings kahaDb more in line with JDBC w.r.t priority and durable subs. Tests now work with both stores.

> Missing messages in durable subscription with selector and KahaDB
> -----------------------------------------------------------------
>
>                 Key: AMQ-2985
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2985
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.4.1
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 5.5.0
>
>
> With a selector and reconnecting durable sub, some messages appear missing as if they were acked in error.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.