[
https://issues.apache.org/jira/browse/AMQ-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-3805.
-----------------------------
Resolution: Fixed
fix in http://svn.apache.org/viewvc?rev=1328413&view=rev
issue with sync between durable sub and prefetch subscription and between
cursor cache fill contention between interleaved dispatch from a transaction
sync and sub activate.
> duplicate dispatch to durable sub with concurrent send transaction commit and
> activate
> --------------------------------------------------------------------------------------
>
> Key: AMQ-3805
> URL: https://issues.apache.org/jira/browse/AMQ-3805
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.5.1
> Reporter: Gary Tully
> Assignee: Gary Tully
> Labels: duplicate, durable, transaction
> Fix For: 5.6.0
>
>
> A durable sub can get duplicate message dispatches when a large send
> transaction is committing and the subscription is activated.
> The completion of the send transaction does a dispatch with the new messages
> already in the store. An activate does a dispatch from the store. The result
> can be duplicate dispatches to the subs pending list. The problem is the
> reset of the audit during activation. The audit should suppress the duplicate
> dispatch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
