Hi Marco What are your JAVA_OPTS? If the -Xms and the Xmx values are not set, it's clear. Normally, from my experience, when you specify Xmx, tomcat stops to allocate more and more memory. But activate the verbose garbage collection. If the garbage collection is alway very quick and tomcat collects more and more memory, there seems to be something strange. I saw once some problems like these with the standard implementation of tomcat from fedora (in use with gcj :-( ). So probably a nice try is to change your java distribution. From performance test we made with java 1.4.X, IBM java has brought the best results to us.
bye Philipp Marco Rossi <[EMAIL PROTECTED]> 01/16/2006 12:17 PM Please respond to "Tomcat Users List" <users@tomcat.apache.org> To Tomcat Users List <users@tomcat.apache.org> cc Subject Re: Jsvc memory management experiences For performance reasons, Tomcat tends to hold onto the memory that it allocates, and reuses it. Interesting enough: but when memory is needed no more, shoud it be collected out and brought it back to the system as available memory, or is is a normal situation that memory once obtained is never released by tomcat ? I'm seeing that free memory is constantly lowering, even there is a no connection to be served, as if garbage collection is never performed. Thanks, Marco --------------------------------- Yahoo! Photos Got holiday prints? See all the ways to get quality prints in your hands ASAP.
