Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 72312 invoked by uid 500); 6 Dec 2002 08:25:01 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 72295 invoked from network); 6 Dec 2002 08:25:00 -0000 From: "Carsten Ziegeler" To: Subject: RE: [C2.1] Memory problem Date: Fri, 6 Dec 2002 09:25:06 +0100 Message-ID: MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <47019.10.0.0.1.1039156037.squirrel@_default_> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal X-MIMETrack: Itemize by SMTP Server on PBSN1/Systeme und Netzwerke(Release 5.0.8 |June 18, 2001) at 06.12.2002 09:25:00, Serialize by Router on PBSN1/Systeme und Netzwerke(Release 5.0.8 |June 18, 2001) at 06.12.2002 09:25:01, Serialize complete at 06.12.2002 09:25:01 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N The last time we profiled Cocoon (3 or 4 months ago)we didn't find a memory leak. I suggest to use a profiling tool. Then you will find very quickly if Cocoon is the problem. Carsten Carsten Ziegeler Open Source Group, S&N AG > -----Original Message----- > From: Antonio Gallardo [mailto:agallardo@agsoftware.dnsalias.com] > Sent: Friday, December 06, 2002 7:27 AM > To: cocoon-dev@xml.apache.org > Subject: [C2.1] Memory problem > > > Hi, > > I think we have detected another "bug" in the current CVS version of 2.1. > > I will try to explain it here: > > As suggested in the book: "Professional Apache Tomcat", ISBN > 1-861007-73-6, page 37, Subtitle "Heap Size". I was configured Tomcat > Engine 4.1.12 with the following params: > > JAVA_OPTS='-Xms256m -Xmx256m -XX:NewSize=128m -XX:MaxNewSize=128m' > > This sustancially improves the performance of the Cocoon engine. The > server serves pages faster. > > But the problem is that is seems like the Java process is slowly "eating" > all the memory. Using the "top" command in Linux and after 2 days of works > the main Java process shows that is using more than 390MB! > > As I noted before in the server are 384 MB of RAM and it runs only Cocoon > Application. We does not use any custom component. All the application is > done using standard XSP logicsheets. > > Can someone has similars problems? Is this a Cocoon problem? > > Thanks in advance, > > Antonio Gallardo. > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org > For additional commands, email: cocoon-dev-help@xml.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org