Howdy, >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.
I see what you mean. I was searching for "leak" or "memory" and found stuff unrelated to this issue. >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 Yup, I was searching for INVALID or WONTFIX resolutions for tomcat 4. >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. ;-) It's a tough one because of the plethora of 3rd party libraries that use such static variables or threads, leaving tomcat without much choice. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
