Besides what Senor Schultz said (which is 100% true), 1. Where is this mentioned in the release notes, and what would one have to search for?
Under KNOWN ISSUES IN THIS RELEASE it does mention issues during web application reloading where shared libraries keep references to objects instantiated by the web application. That says "memory leak" to me although it doesn't specifically say that.
2. You mentioned in your passage the bug was marked as invalid or wontfix, and the bug you gave below is marked as new. So if anyone actually wasted time (like me) looking up what you said, they didn't find it.
All I did was search for "memory leak" under Tomcat 4 and all status. I was not positive that it was marked WONTFIX, I should have clarified that in my original message. I had thought that the issue was something inherent to the design of Tomcat 4 (which was overhauled in Tomcat 5), but I'm sure that they are willing to accept patches if anyone can fix it. ;-)
-Dave
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
