[jira] [Commented] (AMQ-8202) VirtualTopic concurrentSend can break mKahaDB

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

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

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

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

AMQ-8202 - fix concurrency issue on tracking stores in mKahaDB, exposed by virtual topic concurrentSend


> VirtualTopic concurrentSend can break mKahaDB
> ---------------------------------------------
>
>                 Key: AMQ-8202
>                 URL: https://issues.apache.org/jira/browse/AMQ-8202
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.16.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>            Priority: Major
>             Fix For: 5.17.0
>
>
> With a virtual topic doing concurrent send, if the subscription queues are spread across mKahaDB instances, the tracking of message stores can get out of sync with send completion, leaving dangling messages in the store and missing dispatch.
> The issue is lack of thread safety in the mKahadb transaction store. 
> the workaround is to disable concurrentSend
> {code}
> <virtualTopic name="virtual.>" prefix="sub.global.*." concurrentSend="false"/>{code}



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