I've got a question about the tomcat 5.5.25 shared lib…is there any danger of using this almost exclusively if you have a lot of jars that are shared among apps. I know you can but I also saw something somewhere and now again (http://www.digitalsanctum.com/2007/08/18/20-tips-for-using-tomcat-in-production/ - number 6) about garbage collection only operating on memory that was inside the scope of a specific app and because the shared lib stuff doesn’t belong to specific app it wouldn’t get cleaned up. Can anyone confirm this or know anything about this?
I’ve got a jvm in development that has about 20 apps in it…to reduce the heap size, I moved as many jars as I could to the shared lib folder…this reduced the initial heap size dramatically because of the number of jars that are common between apps. However, it seems that the heap size grows rather fast…I didn’t know if there was anything to the idea that garbage collection wouldn’t reclaim shared lib memory…or it may be that this particular jvm just has too much in it again -- Curtis Garman Web Programmer Heartland Community College --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
