I hope Mr. Caldarale answered your question, because you may otherwise be looking at the 800lb Gorilla in the room.
Memory problems within Tomcat could be a number of very hard to see things, but some quick candidates are: * Programmers caching too much data from the DB (or file system) into context attributes * Programmers using context attributes to store session data * Programmers pushing too much data into session attributes * Session timeout is set too high and sessions aren't timing out -----Original Message----- From: Johnson, Trevin (Contractor) [mailto:trevin.john...@occ.treas.gov] Sent: Monday, November 02, 2009 2:53 PM To: 'users@tomcat.apache.org' Subject: Tomcat Memory and Garbage Collection questions... Hello OS Version: Windows 2000 Tomcat version:5.5.17 Initial Memory Pool: 768 Maximum Memory Pool:1024 Java Version: Java\jdk1.5.0_14 When we restart the tomcat service our tomcat memory is about 120Mb. It keeps going up over the next few days util it reaches 700Mb and we have to reboot the server. We do not see any errors just yet but the server gets close to maxing out I have questions around garbage collection for tomcat Questions: 1.We do not see the memory going down for the tomcat service. Shouldn't the memory go down as well as up over this timespan 2.Should the memory get to maximum 768Mb and then go back down or get recycled? 3.Is this a bug or what is normal behavior for the tomcat memory? 4.. How do we implement garbage collection for our windows server(-Xincgc)? I am very new to Tomcat and trying to manage/decrease the memory footprint used by Tomcat? Your help is most appreciated... Thanks trevin.john...@occ.treas.gov --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
