Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A1E7611DB3 for ; Fri, 15 Aug 2014 14:28:18 +0000 (UTC) Received: (qmail 18006 invoked by uid 500); 15 Aug 2014 14:28:18 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 17950 invoked by uid 500); 15 Aug 2014 14:28:18 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 17937 invoked by uid 99); 15 Aug 2014 14:28:18 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Aug 2014 14:28:18 +0000 Date: Fri, 15 Aug 2014 14:28:18 +0000 (UTC) From: "Timothy Bish (JIRA)" To: dev@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMQ-5322) Message is assigned to different client with the same JMSXGroupID MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMQ-5322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14098569#comment-14098569 ] Timothy Bish commented on AMQ-5322: ----------------------------------- You can configure the cache size in your Broker configuration as needed. > 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, GroupIdTest.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.2#6252)