Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 18083 invoked from network); 18 Mar 2009 19:31:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 Mar 2009 19:31:38 -0000 Received: (qmail 56043 invoked by uid 500); 18 Mar 2009 19:31:34 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 56015 invoked by uid 500); 18 Mar 2009 19:31:34 -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 55982 invoked by uid 99); 18 Mar 2009 19:31:34 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Mar 2009 12:31:34 -0700 X-ASF-Spam-Status: No, hits=4.8 required=10.0 tests=DNS_FROM_OPENWHOIS,HTML_MESSAGE,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Mar 2009 19:31:25 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1Lk1Tj-00073s-T1 for users@activemq.apache.org; Wed, 18 Mar 2009 12:31:03 -0700 Message-ID: <22586781.post@talk.nabble.com> Date: Wed, 18 Mar 2009 12:31:03 -0700 (PDT) From: ttmgary To: users@activemq.apache.org Subject: Re: how can I really use more then 1 receiver on the same queue? In-Reply-To: <22534104.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_62682_4838665.1237404663890" X-Nabble-From: gary.watson@ttmsolutions.com References: <22534104.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_62682_4838665.1237404663890 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Seems like setting prefetchPolicy=1 (or greater, if message volume warrants it) should activate your multiple consumer threads. - Gary steve56 wrote: > > > case 2: > - set prefetchPolicy = 0 > - now all threads work consuming sequentially (non in parallel!) > messages. i.e: a thread receives a new message only when the previous > thread do message.acknowledge (or session.commit) > > If I need to process more then 1 messages in parallel with acknowledge > what can I do? > > many thanks > steve56 > > -- View this message in context: http://www.nabble.com/how-can-I-really-use-more-then-1-receiver-on-the-same-queue--tp22534104p22586781.html Sent from the ActiveMQ - User mailing list archive at Nabble.com. ------=_Part_62682_4838665.1237404663890--