Return-Path: Delivered-To: apmail-jakarta-turbine-jcs-user-archive@www.apache.org Received: (qmail 90067 invoked from network); 5 May 2004 15:54:54 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 5 May 2004 15:54:54 -0000 Received: (qmail 31596 invoked by uid 500); 5 May 2004 15:54:32 -0000 Delivered-To: apmail-jakarta-turbine-jcs-user-archive@jakarta.apache.org Received: (qmail 31580 invoked by uid 500); 5 May 2004 15:54:32 -0000 Mailing-List: contact turbine-jcs-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Turbine JCS Users List" Reply-To: "Turbine JCS Users List" Delivered-To: mailing list turbine-jcs-user@jakarta.apache.org Received: (qmail 31530 invoked from network); 5 May 2004 15:54:32 -0000 Received: from unknown (HELO smtp4.wiscmail.wisc.edu) (144.92.197.190) by daedalus.apache.org with SMTP; 5 May 2004 15:54:32 -0000 Received: from conversion-daemon.smtp4.wiscmail.wisc.edu by smtp4.wiscmail.wisc.edu (iPlanet Messaging Server 5.2 HotFix 1.24 (built Dec 19 2003)) id <0HX800G01ZUXR4@smtp4.wiscmail.wisc.edu> (original mail from aasmuts@wisc.edu) for turbine-jcs-user@jakarta.apache.org; Wed, 05 May 2004 10:54:34 -0500 (CDT) Received: from dellpc (c66.168.23.103.mad.wi.charter.com [66.168.23.103]) by smtp4.wiscmail.wisc.edu (iPlanet Messaging Server 5.2 HotFix 1.24 (built Dec 19 2003)) with ESMTPSA id <0HX900G8006XWU@smtp4.wiscmail.wisc.edu> for turbine-jcs-user@jakarta.apache.org; Wed, 05 May 2004 10:54:33 -0500 (CDT) Date: Wed, 05 May 2004 11:00:16 -0500 From: Aaron Smuts Subject: RE: Memory leak problem In-reply-to: <4098C022.2000902@lineone.net> To: 'Turbine JCS Users List' Message-id: <001701c432ba$0eeac7f0$6717a842@smuts> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Mailer: Microsoft Outlook, Build 10.0.2627 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N The shrinker periodically wakes up and looks for expired elements. It doesn't keep the memory under the max. That's done when you put an item into the cache. I think I saw that you had the shrinker come on every few seconds, correct me if I'm wrong. I was afraid that it would keep references to everything if it was always running. Now I'm not sure that could happen. Aaron > -----Original Message----- > From: Matthew Cooke [mailto:mpcooke3@lineone.net] > Sent: Wednesday, May 05, 2004 5:21 AM > To: Turbine JCS Users List > Subject: Memory leak problem > > Aaron, > > I found increasing the JVM to 800meg only delayed the out of memory > problems. I profiled for a while on the production machine but this only > revealed a lot of stacktraces accumulating and these were eventually > thrown away during a GC. > I tried disabling the memory shrinker like you suggested and so far the > JVM hasn't requested an increase above it's starting allocation of 80Meg > which is promising. > > It's still a bit early to be 100% sure, but I was wondering what the > memory shrinker does exactly? Is this the code that keeps the cache > below the maxobjects setting? > > Kind Regards, > Matt. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: turbine-jcs-user-unsubscribe@jakarta.apache.org > For additional commands, e-mail: turbine-jcs-user-help@jakarta.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: turbine-jcs-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: turbine-jcs-user-help@jakarta.apache.org