On 12/13/2010 01:14 PM, Pid wrote: > On 13/12/2010 10:13, Luca Gervasi wrote: >> Hello, >> >> I know that my problem is with the application my tomcat 5.5 powered by > > 5.5.x, where x is what?
Tomcat 5.5.26, i omitted because i'm sure it's a webapp fault. For instance, JVM Version: 1.5.0_17-b04 > >> java 1.5.0_b4 is running. > > That's a really old JVM. Each minor release can contain improvements to > garbage collection algorithms - even new features. If you're stuck with > 1.5, you should try to get the last release. > I'm a sysadmin, i'm not allowed to make change in the enviroment other than the client asks for. I can just "promote" a change. (and did it) >> I have this supposely leeking application that keeps saturating the >> permanent generation. >> >> The problem is an out of memory on the permgen. > > It could just be that your application needs more space allocated in > permgen. How much memory are you assigning to the JVM, what values are > you setting for garbage collection etc? > > I have 1536m of heap, 64Mb (the default, i suppose) allocated for permgen. other options regards the GC only (PrintGC, PrintGCDetails PrintGCTimeStamps). >> Studying the JVM, i understand that the permgen is never sweeped by GC. >> >> My question is: i found the flags combo that enables permgen sweeping. >> Is that a good thing to enable? I can't fix the application right now. > > It's not necessarily going to make a difference. > > Do you reload your application or is it not being actively developed? I used to reload some contextes in the past. Nowdays it's no longer necessary as it goes oom on daily basis. > > > p > Thanks for your time ^^ Luca --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
