Are you actually seeing out of memory exceptions or are you just worried that free memory goes low? If the memory goes low and then is garbage collected that is fine.
Otherwise, I would see what those Hashmap entries are holding on to. My guess would be tickets. You could always shorten the ticket expiration time and run the cleaner more frequently. -Scott On 9/25/07, Dominika Tkaczyk <[EMAIL PROTECTED]> wrote: > > > Scott Battaglia napisał(a): > > > >> Dominika, > >> > >> You can try out YourKit...I believe they have a free trial > version. There > >> is also an Eclipse Profile Plugin. I've only used YourKit and it works > >> well. You would probably want to set it up in a load test environment > (or > >> only very temporarily in production). > > Hello again, > I tried to do some tests with YourKit. It seems that what increases the > most > is the amount of objects (and memory used by them) of > java.util.HashMap$Entry class. Also java.util.HashMap$Entry[] is high in > the > list. > > Another thing I noticed: sometimes when the amount of free memory is > really > low, Tomcat somehow increases it (gets rid of old garbage?). You can see > this effect on this new graph from Munin: > http://logowanie.uw.edu.pl/tomcat_jvm-month.png > The last increase of free memory (to almost 300MB) was not my restart, I > wasn't doing anything on the server at that time. But after the increase > the > same things happen all over again. > > Regards, > Dominika > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas > -- -Scott Battaglia LinkedIn: http://www.linkedin.com/in/scottbattaglia
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
