DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10407>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10407 Tomcat Memory Management ------- Additional Comments From [EMAIL PROTECTED] 2002-08-13 03:51 ------- What you are reporting is not a bug, but here are some comments to help explain what you are seeing. Tomcat Threads --------------- Most all threads (except some tied to a specific Context) in Tomcat are never killed off, they are a resource which are reused. Memory Usage ------------ Total memory usage is not controlled by Tomcat, it is controlled by the JVM. Java does have a System.gc() method to force garbage collection but it is not recommended that applications do this, especially with modern JVM's like those with HotSpot. Tomcat 4 forces one GC, that is immediately after startup just before it starts handling requests. The memory usage for Tomcat varies depending on your applications and the volume of requests handled. The memory usage you see for the java JVM process is dependent upon the memory usage startup options you give to java. Settings such as -Xms for minumum stack size -Xmx for maximum stack size -Xss for thread stack size, etc. It is up to you to properly tune your java memory and gc startup options for the System, OS, and applications running in Tomcat. Here is a document which disucsses memory usage and gc: http://java.sun.com/docs/hotspot/gc/ You should also consider profiling Tomcat running your application using tools like OptimizeIt or JProbe. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
