Gary Tully created AMQ-8202:
-------------------------------
Summary: 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
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)
