Hi Thomas, Actually, we scheduled the garbage collector as a cron job to run every day at night between 2 and 3 o'clock two times to make sure memory is freed up when daily operations start again around 7-8 o'clock. I don't really see how running the garbage collector can have a negative affect? And even if there is a memory leak, how do you explain the high CPU load?
Cheers, Robby -----Oorspronkelijk bericht----- Van: Thomas Markus [mailto:[EMAIL PROTECTED] Verzonden: woensdag, mei 2007 9:26 Aan: [email protected] Onderwerp: Re: Problem with tuning JVM (high CPU load) Hi, looks like a memory leak. maybe the garbage collector runs very often thomas Robby Pelssers schrieb: > > Hi all, > > we have cocoon2.1.10 running on a solaris(OS version5.8). The server > has 16G of memory and 2 processors (sparcv9 processors operating at > 900 MHz). Cocoon is running on tomcat/4.1.24. > > After a while we see our CPU increasing to about 94% and the system > becomes non-responsive. Could anybody point to what we look for? We > can't trace the problem back from the tomcat loggings. > > Cheers, > Robby Pelssers > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
