[
https://issues.apache.org/activemq/browse/AMQ-2439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-2439:
----------------------------
Attachment: amq2439-patch.diff
patch that resolves the duplicate issue, worth a quick review (as I am just
doing a test run atm) of the
org.apache.activemq.network.DemandSubscription.waitForCompletion()
implementation.
I pulled the existing logic for dealing with acks for no subscriptions in
AbstractRegion that was the root cause. With the changes, any acks that don't
have a sub should be considered an error and result in an exception.
will commit pending no issues showing up in my local test run.
> KahaDB + Network of Brokers + Restart = Duplicate Messages that cannot be
> removed from the data store
> -----------------------------------------------------------------------------------------------------
>
> Key: AMQ-2439
> URL: https://issues.apache.org/activemq/browse/AMQ-2439
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, Message Store
> Reporter: Hiram Chirino
> Assignee: Rob Davies
> Fix For: 5.3.0
>
> Attachments: amq2439-patch.diff
>
>
> Every time the broker is restarted, the same set of duplicate messages get
> redelivered to consumers.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
