[
https://issues.apache.org/jira/browse/AMQ-3891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13407952#comment-13407952
]
Timothy Bish commented on AMQ-3891:
-----------------------------------
NMS doesn't have the duplicate suppression features that the Java client has so
its probable that this is normal behavior. We'd need a JUnit test case that
reproduces the issue to show that its not just a limitation of the NMS client
at play.
> Durable subscribers receiving duplicate messages
> ------------------------------------------------
>
> Key: AMQ-3891
> URL: https://issues.apache.org/jira/browse/AMQ-3891
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.5.1, 5.6.0
> Reporter: Emil Kongelys
> Priority: Critical
>
> This is what it seems to take to reproduce this:
> • The durable subscriber is connected to the message broker, using
> the failover protocol
> • The message broker is then restarted (with the client running)
> • The client application is then restarted
> o The client now receives two copies of every message!
> • Try restarting the client again
> o The client now receives three copies of every message!
> • And so on...
--
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
