Return-Path: Delivered-To: apmail-geronimo-activemq-users-archive@www.apache.org Received: (qmail 15504 invoked from network); 13 Jun 2006 14:32:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 13 Jun 2006 14:32:39 -0000 Received: (qmail 30360 invoked by uid 500); 13 Jun 2006 14:32:38 -0000 Delivered-To: apmail-geronimo-activemq-users-archive@geronimo.apache.org Received: (qmail 30337 invoked by uid 500); 13 Jun 2006 14:32:38 -0000 Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: activemq-users@geronimo.apache.org Delivered-To: mailing list activemq-users@geronimo.apache.org Received: (qmail 30328 invoked by uid 99); 13 Jun 2006 14:32:38 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Jun 2006 07:32:38 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of lists@nabble.com designates 72.21.53.35 as permitted sender) Received: from [72.21.53.35] (HELO talk.nabble.com) (72.21.53.35) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Jun 2006 07:32:35 -0700 Received: from localhost ([127.0.0.1] helo=talk.nabble.com) by talk.nabble.com with esmtp (Exim 4.50) id 1Fq9wF-0000jF-9r for activemq-users@geronimo.apache.org; Tue, 13 Jun 2006 07:32:15 -0700 Message-ID: <4847821.post@talk.nabble.com> Date: Tue, 13 Jun 2006 07:32:15 -0700 (PDT) From: jevans12 To: activemq-users@geronimo.apache.org Subject: Re: 4.0 Consumer OutOfMemoryError bug? In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-Sender: jevans12@harris.com X-Nabble-From: jevans12 References: <4636181.post@talk.nabble.com> <4645070.post@talk.nabble.com> <4647038.post@talk.nabble.com> <4650934.post@talk.nabble.com> <4652810.post@talk.nabble.com> <4669553.post@talk.nabble.com> <4733986.post@talk.nabble.com> <4761710.post@talk.nabble.com> <4798340.post@talk.nabble.com> <4822824.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Are prefetch policy and optimized ack's Autonomous? As I see a consumer will ask for 65% of the prefetch policy messages. Does the batching of ack's follow this? as I receive the 65th (of 100) message a batch ack will be sent for those 65? -- View this message in context: http://www.nabble.com/4.0-Consumer-OutOfMemoryError-bug--t1707655.html#a4847821 Sent from the ActiveMQ - User forum at Nabble.com.