Return-Path: X-Original-To: apmail-activemq-users-archive@www.apache.org Delivered-To: apmail-activemq-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C2EB4187C4 for ; Mon, 16 Nov 2015 17:38:37 +0000 (UTC) Received: (qmail 72934 invoked by uid 500); 16 Nov 2015 17:38:37 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 72892 invoked by uid 500); 16 Nov 2015 17:38:37 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 72875 invoked by uid 99); 16 Nov 2015 17:38:36 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Nov 2015 17:38:36 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 66508180A60 for ; Mon, 16 Nov 2015 17:38:36 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 4.314 X-Spam-Level: **** X-Spam-Status: No, score=4.314 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URI_HEX=1.313, URI_TRY_3LD=0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=dowjones_com.20150623.gappssmtp.com Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id P5QRVZkJE9Up for ; Mon, 16 Nov 2015 17:38:26 +0000 (UTC) Received: from mail-oi0-f52.google.com (mail-oi0-f52.google.com [209.85.218.52]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 2B8EE24B15 for ; Mon, 16 Nov 2015 17:38:25 +0000 (UTC) Received: by oiww189 with SMTP id w189so87811151oiw.3 for ; Mon, 16 Nov 2015 09:38:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dowjones_com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=ze6EWmyltkOSnKIpfWrU9tkHEQVSZZxyyFTe0KgiCMI=; b=Sqx8HDzdjar0xnHPTAKbHY0nCDXUYMVZm65YFkaWD1/ne3rpgO72UQusNKPdGYlkD0 nnXABO5S8e/lAFocWydoj/3GfCDX7d1kjvMu204Ual5dUdvFii83juvhPxlx69V1AmLb afsaPmSBZFB28MJWiCSuy5uxgjAFNS/oymK66SDQO0jgKnwkHQwOzIjMZowUUBwZDAp2 EIEMSfJEw3DUjQ6QUOZmEcIcR4RW1F+mIgtTWvC3z2hG9N/M+VRSS+uMgpRri1hJm1J6 KLlemNX/26eTXBuW/2RYu7045muH0+u1XMlZrhIX2tzbADt3FjA5nfzQCFprDE758ztf N0pA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=ze6EWmyltkOSnKIpfWrU9tkHEQVSZZxyyFTe0KgiCMI=; b=NSkKJvjH5bJgd5mjJM884DeNmv4/U62xd5MklZAxNwnG32IYMSDxfUfF0joH+Amw1B XLsAjBv7D9KzZzzA3MU/WqJkVg/+TXRWgsYvLMd7KXob3Q9/Txlb7pNIenH58l5n9PXI 96wHPxjCG5RTgElyuDPtAPPj7iDheIGn933A3Y4TSyAu+V9OuhknBlhV0DbD35zhS2Pz 8KuDJRObFv91DobRHyRfFAI+qaat9thURUkcE8Abf8GHPHJS+wOm5YvDAcm0phOAlmkd Gp1xeRMztsjCIoVfqIR/Q50ub+SVhRQjfGaI46JYJSrQW12Z0BjminN3mjQqZeuYCo7w j4sw== X-Gm-Message-State: ALoCoQlIHVRkcGtGv/+chqY0mY9RsFu8uRuj2S5SQmy1pj1+Lg+a3iidmWDBfmlBS9dzb4wHpDr4 MIME-Version: 1.0 X-Received: by 10.202.213.133 with SMTP id m127mr21148561oig.26.1447695503906; Mon, 16 Nov 2015 09:38:23 -0800 (PST) Received: by 10.202.214.146 with HTTP; Mon, 16 Nov 2015 09:38:23 -0800 (PST) In-Reply-To: References: <1447189560037-4703823.post@n4.nabble.com> Date: Mon, 16 Nov 2015 12:38:23 -0500 Message-ID: Subject: Re: Message Group rebalancing From: "Takawale, Pankaj" To: users@activemq.apache.org Content-Type: multipart/alternative; boundary=001a113b03ca40fdbf0524abe078 --001a113b03ca40fdbf0524abe078 Content-Type: text/plain; charset=UTF-8 You could achieve it from your application logic. You could have your producer or consumers break the JMSXGroupID stickiness by sending JMSXGroupSeq=-1 message after producing or receiving N messages from the same groupID. After stickiness break up, new consumers would get a chance to acquire the groups. On Wed, Nov 11, 2015 at 9:49 AM, Rob Davies wrote: > Nice feature - submit a JIRA! > > > On 11 Nov 2015, at 14:28, Tim Bain wrote: > > > > I've never heard of such a feature (but maybe someone else here has), > but I > > think it would be a great addition if it doesn't exist. So if you don't > > get a response within a couple days, I encourage you to submit an > > enhancement request in JIRA. > > > > Tim > > On Nov 10, 2015 2:20 PM, "sspind" wrote: > > > >> Hi there, > >> > >> a question related to message groups: is it possible to rebalance > message > >> groups when a new consumer registers with the broker? > >> In my setup I have two consumers that consume from the same queue where > all > >> messages have a message group ID. If one consumer loses connection all > >> messages go to the other. If the consumer reconnects messages will > still go > >> to the other one. At least if the broker saw the respective group ID > >> already. I know that new messages will again be given to either of the > >> consumers. However, in my scenario there is only a relatively small set > of > >> "long lived" group IDs. So it can happen that all messages will be > routed > >> to > >> one consumer while the other one is idle. > >> > >> Looking forward to your replies! > >> > >> sspind > >> > >> > >> > >> -- > >> View this message in context: > >> > http://activemq.2283324.n4.nabble.com/Message-Group-rebalancing-tp4703823.html > >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. > >> > > --001a113b03ca40fdbf0524abe078--