AW: AW: OutOfMemoryError

[Christofer Dutz]

Hi Oleg   Well exactly this is why I used JRockit, because I didn’t want to bother finding out how to tweak it ;) I know that the way the Garbagecollector works can be configured using command-line parameters, but I don’t know which ones and if they have the desired effect. I just wanted to give you the hint that you will not find any real memory-leaks, because there aren’t any and that the problems you are having result of a garbage collection problem in the VM … realizing this earlier would have made many many days of code-checking and profiling obsolete L   Good luck,      Chris   [ c h r i s t o f e r   d u t z ]   IT-Berater univativ GmbH & Co. KG Robert-Bosch-Str. 7, 64293 Darmstadt   fon: 0 61 51 / 66 717 - 21 fax: 0 61 51 / 66 717 - 29 email: [EMAIL PROTECTED] http://www.univativ.de   Darmstadt, Stuttgart, Karlsruhe, Düsseldorf     Von: Oleg Konovalov [mailto:[EMAIL PROTECTED] Gesendet: Montag, 10. Juli 2006 18:12 An: users@cocoon.apache.org Betreff: Re: AW: OutOfMemoryError   Christofer, Could you please elaborate on "We could have solved this by tweaking the GC settings of the VM..." I do not think we have an option of switching to BEA Jrockit VM. We can only use Sun's JavaVM (1.4.2) Also I found out (from another dev group) that the primary suspect is a new application which is not a Cocoon one, but WebWorks. Any know memory issues for WebWorks apps ? (I do realize that's a Cocoon mailing list, sorry...  All other apps there are Cocoon ones.)   Thank you, Oleg.   ----- Original Message ---- From: Christofer Dutz <[EMAIL PROTECTED]> To: users@cocoon.apache.org; Oleg Konovalov <[EMAIL PROTECTED]> Sent: Monday, July 10, 2006 3:50:27 AM Subject: AW: OutOfMemoryError Hi Oleg,   we encountered similar problems and fortunately found our that these problems were VM related. I assume you are using a standard Sun JDK installation (This was the case with our system). When looking at the VM memory consumption, we could see an increasing memory consumption. Whenever we manually triggered a “big garbage-collection” most of this was freed again. The problem is that the default Garbage Collection Settings seem to have problems with circular references. Memory, which is not accessible, is not freed because of this. We could have solved this by tweaking the GC settings of the VM, but we got rid of the problems by using the BEA Jrockit VM instead (I knew this would work and I didn’t want to dig into all the switches an leavers of the sun GC)   Hope this helps.   Regards,             Christofer   [ c h r i s t o f e r   d u t z ]   IT-Berater univativ GmbH & Co. KG Robert-Bosch-Str. 7, 64293 Darmstadt   fon: 0 61 51 / 66 717 - 21 fax: 0 61 51 / 66 717 - 29 email: [EMAIL PROTECTED] http://www.univativ.de   Darmstadt, Stuttgart, Karlsruhe, Düsseldorf     Von: Oleg Konovalov [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 7. Juli 2006 16:07 An: cocoon list Betreff: OutOfMemoryError   Hi, We are getting OutOfMemoryError 16:26:41,011 ERROR [STDERR] java.lang.OutOfMemoryError in our production server (which has 4GB of RAM, javaVM - max 2GB) every other day. All applications stop responding. We have a bunch of Cocoon applications [mostly 2.0.4] running on JBoss3.0.7. It is totally unclear which application is causing the problem. I don't remember that problem happening in our Development or Testing environment (where max JavaVM=512MB), but I guess it has a much lighter load. Is there any known memory problem with Cocoon ? Is there a way to do memory profiling of Cocoon Apps ? Any particular tool ? (I have done memory profiling of Java applets with JProbe years ago)   Any advice is very appreciated. Thank you in advance,  Oleg.