Return-Path: Delivered-To: apmail-geronimo-activemq-users-archive@www.apache.org Received: (qmail 2170 invoked from network); 31 May 2006 16:25:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 31 May 2006 16:25:39 -0000 Received: (qmail 90327 invoked by uid 500); 31 May 2006 16:25:39 -0000 Delivered-To: apmail-geronimo-activemq-users-archive@geronimo.apache.org Received: (qmail 90308 invoked by uid 500); 31 May 2006 16:25: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 90299 invoked by uid 99); 31 May 2006 16:25:38 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 May 2006 09:25: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; Wed, 31 May 2006 09:25:38 -0700 Received: from localhost ([127.0.0.1] helo=talk.nabble.com) by talk.nabble.com with esmtp (Exim 4.50) id 1FlTVV-0005KP-KD for activemq-users@geronimo.apache.org; Wed, 31 May 2006 09:25:17 -0700 Message-ID: <4647038.post@talk.nabble.com> Date: Wed, 31 May 2006 09:25:17 -0700 (PDT) From: skarthik 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: karthik.sethuraman@necam.com X-Nabble-From: skarthik References: <4636181.post@talk.nabble.com> <4645070.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 Hi James, Well I read the information on prefetch limit (the link you specified) and iIMHO I don't believe that is the issue. First, I lowered the rate of messages published to 1 per second and I still see the heap size growing at the same rate (per KB of messages received) and it eventually hits the OutOfMemoryError. There is only one publisher and one consumer connected the JMS server. Second my consumer is a test program and is very fast. All it does is display the messages received. Also the log time of the published messages (logged by producer before publish) and received messages (logged by consumer after received) are the same (down to the last millisecond). I do feel there maybe a critical memory leak somewhere. Also as I mentioned in my previous post, the RC2 build does not have this problem. thanks karthik -- View this message in context: http://www.nabble.com/4.0+Consumer+OutOfMemoryError+bug--t1707655.html#a4647038 Sent from the ActiveMQ - User forum at Nabble.com.