Return-Path: Delivered-To: apmail-geronimo-activemq-dev-archive@www.apache.org Received: (qmail 34416 invoked from network); 29 Nov 2006 02:57:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Nov 2006 02:57:32 -0000 Received: (qmail 67358 invoked by uid 500); 29 Nov 2006 02:57:41 -0000 Delivered-To: apmail-geronimo-activemq-dev-archive@geronimo.apache.org Received: (qmail 67334 invoked by uid 500); 29 Nov 2006 02:57:41 -0000 Mailing-List: contact activemq-dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: activemq-dev@geronimo.apache.org Delivered-To: mailing list activemq-dev@geronimo.apache.org Received: (qmail 67325 invoked by uid 99); 29 Nov 2006 02:57:41 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Nov 2006 18:57:41 -0800 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 (herse.apache.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, 28 Nov 2006 18:57:28 -0800 Received: from [72.21.53.38] (helo=jubjub.nabble.com) by talk.nabble.com with esmtp (Exim 4.50) id 1GpFdE-0000CF-6Z for activemq-dev@geronimo.apache.org; Tue, 28 Nov 2006 18:57:08 -0800 Message-ID: <7592496.post@talk.nabble.com> Date: Tue, 28 Nov 2006 18:57:08 -0800 (PST) From: "jk@penguinsfan.com" To: activemq-dev@geronimo.apache.org Subject: Heap overflow after consumer closes MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: jk@penguinsfan.com X-Virus-Checked: Checked by ClamAV on apache.org This is with the Kaha store and the store durable pending cursor. Messages size is 10 kilobytes. Heap size set to 512MB. activemq.xml configured for 100 MB. 1. Start a consumer for a durable topic and stop it immediately. 2. Wait until 50000 messages have been enqueued. 3. Start the producer for the durable topic (leave it running for remainder of test). 4. Restart the consumer from Step #1, have it consume 8000 messages. 5. Once the consumer has ended, heap usage will rise until out of heap (forcing GC does not affect). UsageManager only indicates approx 1% memory usage, so this leak is outside of what UsageManager monitors. Memory usage was about 80 MB at the time the consumer closed, and rose to > 500 MB within one minute of the consumer closing. -- View this message in context: http://www.nabble.com/Heap-overflow-after-consumer-closes-tf2722488.html#a7592496 Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.