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=26135>. 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=26135 Tomcat 5.0.16 leaks memory when a webapp is reloaded or stopped/started [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[EMAIL PROTECTED] Status|RESOLVED |REOPENED Resolution|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2004-01-28 23:54 ------- I believe this is a bug within Tomcat... Here is a way to replicate it: Use the Struts blank war. Available here: http://mirrors.isc.org/pub/apache/jakarta/struts/binaries/jakarta-struts-1.1.zip Load that webapp, and open two browser windows, one to the Tomcat Manager and one to the Tomcat Status page. View the available memory. You will see it cycle within a meg as garbage collection is run. Then use Tomcat Manager to reload the struts webapp. The free memory should now be a meg less. This will continue until you reach 0, when a major garbage collection will occur, but it just looks like memory is released, as the Total Memory usage has now increased. You can continue this cycle until the memory reaches the total allocated, and Tomcat will fall over. If this is truly a "non issue", then I feel the Tomcat developers need to answer this issue more directly (like the release notes). We have customers that run multiple occurrences of our webapp under a single Tomcat, and need to reload... With the leak... they end up having to restart Tomcat to free the memory... causing support issues. I look forward to become more educated on why this is (not) an issue... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]