From activemq-users-return-5006-apmail-geronimo-activemq-users-archive=geronimo.apache.org@geronimo.apache.org Thu Oct 12 20:09:15 2006 Return-Path: Delivered-To: apmail-geronimo-activemq-users-archive@www.apache.org Received: (qmail 41329 invoked from network); 12 Oct 2006 20:09:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 12 Oct 2006 20:09:15 -0000 Received: (qmail 52668 invoked by uid 500); 12 Oct 2006 20:09:14 -0000 Delivered-To: apmail-geronimo-activemq-users-archive@geronimo.apache.org Received: (qmail 52649 invoked by uid 500); 12 Oct 2006 20:09:14 -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 52640 invoked by uid 99); 12 Oct 2006 20:09:14 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Oct 2006 13:09:14 -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; Thu, 12 Oct 2006 13:09:13 -0700 Received: from [72.21.53.38] (helo=jubjub.nabble.com) by talk.nabble.com with esmtp (Exim 4.50) id 1GY6rN-0007pI-89 for activemq-users@geronimo.apache.org; Thu, 12 Oct 2006 13:08:53 -0700 Message-ID: <6783729.post@talk.nabble.com> Date: Thu, 12 Oct 2006 13:08:53 -0700 (PDT) From: yaussy To: activemq-users@geronimo.apache.org Subject: Re: Controlling memory usage for persistent messages In-Reply-To: <0C8D2C7F-2A6D-46D3-B004-F5C815400EE2@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: yaussy@cboe.com References: <6640467.post@talk.nabble.com> <6735220.post@talk.nabble.com> <0C8D2C7F-2A6D-46D3-B004-F5C815400EE2@gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Thanks, Rob. Is this in the current 4.1 build? I will try it out... rajdavies wrote: > > keeping messages in memory pending dispatch will be optional for the > 4.1 GA version of activemq > > cheers, > > Rob > On 10 Oct 2006, at 13:22, terrytriple wrote: > >> >> Afraid I can't help with your question, but I'm looking for an >> answer to the >> same question ! >> >> We are thinking of moving from a JBossMQ solution to ActiveMQ -- >> but having >> the broker block/throw exceptions because it's out of memory due to it >> holding all the messages in memory is a real problem for us. With our >> existing solution we sometimes have hundreds of thousands of messages >> waiting around. >> >> anyway - looking forward to any reponse to this issue ! >> >> >> yaussy wrote: >>> >>> When sending persistent messages (durable topics) to a consumer, >>> and then >>> the consumer goes away, AMQ 4.x broker consumes memory. Is there >>> any way >>> to configure how much it will attempt to keep in memory for >>> persistent >>> messages?? Seems to me that's the point of having the persistence >>> mechanism (i.e. derby or kaha or Oracle) - capacity at that level >>> is not >>> an issue. I can't have the Broker attempting to keep all messages >>> ready >>> in memory for that failed consumer - it may run out of memory very >>> quickly. >>> >> >> -- >> View this message in context: http://www.nabble.com/Controlling- >> memory-usage-for-persistent-messages-tf2382626.html#a6735220 >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >> > > > -- View this message in context: http://www.nabble.com/Controlling-memory-usage-for-persistent-messages-tf2382626.html#a6783729 Sent from the ActiveMQ - User mailing list archive at Nabble.com.