[jira] [Commented] (AMQ-6406) kahadb concurrentStoreAndDispatch - duplicate suppression in cursor needs to wait for possible store add

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on AMQ-6406:
------------------------------------------------------

Commit 1d1c9262fdd224dcca744b729bebe8cf4e13c3ef in activemq's branch refs/heads/activemq-5.14.x from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=1d1c926 ]

AMQ-6406 - ensure duplicates trapped by the cursor-add or queue-page-in are removed from the message store

(cherry picked from commit 2b1cda196471280c4fc587d8664d6373e18c97ca)


> kahadb concurrentStoreAndDispatch - duplicate suppression in cursor needs to wait for possible store add
> --------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-6406
>                 URL: https://issues.apache.org/jira/browse/AMQ-6406
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: KahaDB
>    Affects Versions: 5.14.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 5.14.1, 5.15.0
>
>
> An inflight store add that is a duplicate may get suppressed by the index or may get added as a duplicate if the original has already been dispatched and acked.
> If the cursor traps the duplicate message, it won't get dispatched so it needs to get removed from the store. 
> Otherwise it will remain till restart and possibly get redispatched and/or hold up gc.
> The store removal is only occurring for the jdbc store (that has no separate index to track duplicates). This needs fixing.



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