You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2017/03/21 16:12:41 UTC
[jira] [Closed] (AMQ-6634) Restarting Consumer results in duplicate
message delivery for all messages consumed after restart.
[ https://issues.apache.org/jira/browse/AMQ-6634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish closed AMQ-6634.
-----------------------------
Resolution: Invalid
Targets a very old version and provides no test to run against newer release. Better to ask on the users mailing list for help, and also move to a new release with latest fixes.
> Restarting Consumer results in duplicate message delivery for all messages consumed after restart.
> --------------------------------------------------------------------------------------------------
>
> Key: AMQ-6634
> URL: https://issues.apache.org/jira/browse/AMQ-6634
> Project: ActiveMQ
> Issue Type: Bug
> Components: JMS client
> Affects Versions: 5.7.0
> Environment: Linux
> Reporter: Jayaram Sankaranarayanan
>
> This is observed during our tests where a consumer is restarted , after which we see that consumer receives duplicate messages for all the messages sent post restart.
> Here is the test environment.
> Active MQ 5.7.0
> One Topic, with two active consumers and one producer.
> There are three JVM instances.
> 1. Runs the broker,
> 2. Runs the producer and consumer#1
> 3. Runs the consumer#2
> When instance#3 is restarted, that consumer will start receiving duplicate messages for all the messages that producer sends (instance#2).
> Note that consumer running in instance #2 (which was not restarted) does not receive duplicate messages.
> The duplicate message delivery is not just for those messages that producer sends when consumer#2 was being restarted. It is observed for all the messages that producer sends after consumer#2 is back online as well.
> Can you please confirm whether this is a known issue with activeMQ 5.7 ?
> I tried to search the issues in JIRA but could not see a matching one.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)