> -----Original Message-----
> From: David Rees [mailto:[EMAIL PROTECTED]
> Sent: December 2, 2003 11:01 AM
> To: Tomcat Users List
> Subject: Re: Tomcat 4.0.x memory leak (not javac)
>
> Shapira, Yoav wrote:
> > 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. ;-)
Bugzilla is obviously not working sometimes. I searched for "memory leak" one
time and got it. Then I went to search for it for someone else so I could
give them the bug number but nothing came up. I did the exact same search,
"memory leak". Very interesting indeed. Heck, I even searched for just
"memory" or "leak" once each and came up with nothing.
>
> -Dave
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
__
This communication is intended for the use of the recipient to whom it
is addressed, and may contain confidential, personal, and or privileged
information. Please contact us immediately if you are not the intended
recipient of this communication, and do not copy, distribute, or take
action relying on it. Any communications received in error, or
subsequent reply, should be deleted or destroyed.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
