[
https://issues.apache.org/jira/browse/AMQ-5322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14190095#comment-14190095
]
Igor Samardzija edited comment on AMQ-5322 at 10/31/14 8:31 AM:
----------------------------------------------------------------
Java classes attached. Test provided.
Listener scenario with message groups (3 consumers)
was (Author: samara):
Listener scenario with message groups (3 consumers)
> Message is assigned to different client with the same JMSXGroupID
> -----------------------------------------------------------------
>
> Key: AMQ-5322
> URL: https://issues.apache.org/jira/browse/AMQ-5322
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.9.0, 5.9.1, 5.10.0
> Reporter: wesley lin
> Attachments: AMQ5322Test.java, Consumer.java, GroupIdTest.java,
> Producer.java, TestGroups.java
>
>
> I discovered since AMQ 5.9, message could be sent to different consumer even
> with JMSXGroupID is set.
> Here is how to reproduce.
> 1. start 10 consumers to connect to server (consumer 1-10)
> 2. send 1025 messages with JMSXGroupID set from 0 - 1024
> 3. add other 10 consumers to connect to server (consumer 11-20)
> 4. send several messages with JMSXGroup set from 0 - 1024
> Now, you can observe consumers added lately ( 11 - 20 ) will also receive
> messages even JMSXGroupID have been dispatched to first consumer group( 1 -
> 10).
>
> note: In step2 , there should have more than 1024 different kind of
> JMSXGroupID to reproduce this bug.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
