Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 82258 invoked from network); 11 Mar 2006 09:10:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 11 Mar 2006 09:10:50 -0000 Received: (qmail 67620 invoked by uid 500); 11 Mar 2006 09:10:47 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 67081 invoked by uid 500); 11 Mar 2006 09:10:45 -0000 Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: users@cocoon.apache.org List-Id: Delivered-To: mailing list users@cocoon.apache.org Received: (qmail 67069 invoked by uid 99); 11 Mar 2006 09:10:45 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 11 Mar 2006 01:10:45 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [85.197.127.214] (HELO mail.c-ware.de) (85.197.127.214) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 11 Mar 2006 01:10:44 -0800 Received: (qmail 6121 invoked from network); 11 Mar 2006 08:16:35 -0000 Received: from unknown (HELO TIESTO) (84.167.77.227) by 0 with SMTP; 11 Mar 2006 08:16:35 -0000 From: "Christofer Dutz" To: , Subject: AW: AW: Memoryleaks in Cocoon 2.1.7? Date: Sat, 11 Mar 2006 10:10:17 +0100 Message-ID: <001b01c644eb$9d60adc0$0e2aa8c0@TIESTO> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-2" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <44124EF3.3090000@dslextreme.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 thread-index: AcZEuwFqvZYg8SXLRUSpCH/1BfWQhgAMJZXQ X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Yes -----Urspr=FCngliche Nachricht----- Von: Ralph Goers [mailto:Ralph.Goers@dslextreme.com]=20 Gesendet: Samstag, 11. M=E4rz 2006 05:16 An: users@cocoon.apache.org Betreff: Re: AW: Memoryleaks in Cocoon 2.1.7? Were you using Java 5? Christofer Dutz wrote: > > Well it seems that I was able to get rid of the nasty memory leaks. > > The problem is, that they weren't real memory leaks after all. I=20 > noticed that if I pressed the "GC" button in the JConsole tool, that=20 > all unnecessary Memory was freed. As far as could find out, this is a=20 > problem with the default garbage collection method used to free=20 > memory. This uses a fast but inaccurate way to free unused memory=20 > blocks. I could have started testing out different GC settings, but I=20 > simply witched to a JRockit VM and all my memory problems were solved. = > After doing some performance evaluations at my university I knew that=20 > JRockit seems to handle its memory a lot more efficient than the Sun=20 > VM (both with default GC setting), so I didn't bother testing the=20 > settings of the Sun VM. Maybe someone on this list has some hints to=20 > getting the Sun VM to clean up its memory better. > > Hope this helps anyone. > > Chris > > = ------------------------------------------------------------------------ > > *Von:* Simone Gianni [mailto:s.gianni@thebug.it] > *Gesendet:* Donnerstag, 2. M=E4rz 2006 13:14 > *An:* users@cocoon.apache.org > *Betreff:* Re: Memoryleaks in Cocoon 2.1.7? > > Just for the records, i'm currently experiencing some out of memory=20 > errors on a cocoon 2.1.8 using common blocks + forms + fop on two=20 > machines (a developer machine running windows, and a gentoo server),=20 > while with the same cocoon version and same application it does not=20 > happen on other machines (ranging from ubuntu and gentoo developers=20 > machines, and an ubuntu server). So I thought it was a platform=20 > problem, not directly related with cocoon (so didn't even tried a=20 > profiled run), but since the thread is open and i have two machines=20 > showing random out of memory, let me know if i can check something to=20 > make it clearer. > > Simone > > Tomasz Nowak wrote: > > U=BFytkownik wrote: > =20 >> I have read your posts. The problem seems to be a different one. >> =20 >> We increased the memory assigned to tomcat and cocoon and = successfully >> increased the time between OutOfMemory errors. With 2GB of Memory the >> application runs stable for about one week. I am now looking for the >> leak itself and as I can see in the jconsole there is deffinitively a >> leak. If I cant get a tip here, my next step is to setup a profiler >> and run jmeter stresstests untill I find the bug. Hopefully it is no >> "big-one" in cocoon itself. >> =20 > =20 > I would be VERY THANKFULL if you let me know if you find that leak. > =20 > =20 > > --=20 > Simone Gianni > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org For additional commands, e-mail: users-help@cocoon.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org For additional commands, e-mail: users-help@cocoon.apache.org