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 2019/09/26 14:56:00 UTC

[jira] [Commented] (AMQ-7311) KahaDB XA topic recovered pending ack tracking is store wide, needs to be per subscription key

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

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

Commit ed5edb03d7fe63ef27269566aaa9a9b501650eb0 in activemq's branch refs/heads/master from gtully
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=ed5edb0 ]

AMQ-7311 - track recovered prepared ack locations on a per subscriber basis, fix and test


> KahaDB XA topic recovered pending ack tracking is store wide, needs to be per subscription key 
> -----------------------------------------------------------------------------------------------
>
>                 Key: AMQ-7311
>                 URL: https://issues.apache.org/jira/browse/AMQ-7311
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: KahaDB, XA
>    Affects Versions: 5.15.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>            Priority: Major
>             Fix For: 5.16.0
>
>
> With two durable subs, one with a recovered prepared ack XA transaction, the second sub cannot access the messages.
> The xa recovered_prepared_ack tracking per messageId needs to be per subscriber rather than store wide.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)