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 9165317AB0 for ; Fri, 6 Mar 2015 02:02:57 +0000 (UTC) Received: (qmail 39479 invoked by uid 500); 6 Mar 2015 02:02:54 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 39433 invoked by uid 500); 6 Mar 2015 02:02:54 -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 39422 invoked by uid 99); 6 Mar 2015 02:02:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Mar 2015 02:02:53 +0000 X-ASF-Spam-Status: No, hits=1.6 required=5.0 tests=URI_HEX,URI_TRY_3LD X-Spam-Check-By: apache.org Received-SPF: error (athena.apache.org: local policy) Received: from [162.253.133.43] (HELO mwork.nabble.com) (162.253.133.43) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Mar 2015 02:02:48 +0000 Received: from mjoe.nabble.com (unknown [162.253.133.57]) by mwork.nabble.com (Postfix) with ESMTP id 97A42161582E for ; Thu, 5 Mar 2015 18:01:40 -0800 (PST) Date: Thu, 5 Mar 2015 17:53:05 -0800 (PST) From: artnaseef To: users@activemq.apache.org Message-ID: <1425606785484-4692580.post@n4.nabble.com> In-Reply-To: References: <1425567500269-4692555.post@n4.nabble.com> Subject: Re: consume one MessageGroup by several consumers MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Selectors would work, but I recommend to avoid them - they can lead to confusion and problems. For example, adding consumers with selectors to a queue with a large backlog of messages means every one of those messages must be evaluated against the selector to see if it matches, hurting performance. Also, one question that comes up often on the boards - "I have unconsumed messages" - and selectors sometimes lead to this confusion. For the Op -- is it possible to rework the solution to use two different queues? Queues are just that - a first-in, first-out structure for messages. If two sets of messages should not affect each other, then separate queues is likely the best approach. -- View this message in context: http://activemq.2283324.n4.nabble.com/consume-one-MessageGroup-by-several-consumers-tp4692555p4692580.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.