Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 2282 invoked from network); 16 Nov 2009 08:33:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 16 Nov 2009 08:33:17 -0000 Received: (qmail 67811 invoked by uid 500); 16 Nov 2009 08:33:17 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 67749 invoked by uid 500); 16 Nov 2009 08:33:16 -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 67617 invoked by uid 99); 16 Nov 2009 08:33:16 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Nov 2009 08:33:16 +0000 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 (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; Mon, 16 Nov 2009 08:33:07 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1N9x0w-0003jV-6B for users@activemq.apache.org; Mon, 16 Nov 2009 00:32:46 -0800 Message-ID: <26368295.post@talk.nabble.com> Date: Mon, 16 Nov 2009 00:32:46 -0800 (PST) From: Daroo To: users@activemq.apache.org Subject: Re: ActiveMQ 5.3.0 OutOfMemoryError In-Reply-To: <26340339.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: dariusz.szablinski@gmail.com References: <26340339.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org Hi, I was also getting the same exception while using KahaDB as persistance adapter and producer flow control off, but it seems to be fixed in the latest 5.4.0 snapshot. I'm not sure, but maybe that was the issue: https://issues.apache.org/activemq/browse/AMQ-2481 -- View this message in context: http://old.nabble.com/ActiveMQ-5.3.0-OutOfMemoryError-tp26340339p26368295.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.