tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Filip Hanik" <devli...@hanik.com>
Subject Re: Tomcat 4.0.x memory leak (not javac)
Date Tue, 02 Dec 2003 19:03:54 GMT
download a trial of JProbe :)

Filip
----- Original Message -----
From: "Trenton D. Adams" <trenta@athabascau.ca>
To: "'Tomcat Users List'" <tomcat-user@jakarta.apache.org>
Sent: Tuesday, December 02, 2003 11:08 AM
Subject: RE: Tomcat 4.0.x memory leak (not javac)


Ouch, LOL.  I don't really know a whole lot about the tomcat "under the
hood"!
:)

I can try though.  Do you have a procedure that I should take to find this?
Is there a debugging option that I can turn on for tomcat?

> -----Original Message-----
> From: Shapira, Yoav [mailto:Yoav.Shapira@mpi.com]
> Sent: December 2, 2003 11:45 AM
> To: Tomcat Users List
> Subject: RE: Tomcat 4.0.x memory leak (not javac)
>
>
> Howdy,
> Since you can reproduce your error easily, can you narrow
> down which 3rd
> party library is keeping the references that cause the memory leak?
>
> Yoav Shapira
> Millennium ChemInformatics
>
>
> >-----Original Message-----
> >From: Trenton D. Adams [mailto:trenta@athabascau.ca]
> >Sent: Tuesday, December 02, 2003 1:43 PM
> >To: 'Tomcat Users List'
> >Subject: RE: Tomcat 4.0.x memory leak (not javac)
> >
> >> -----Original Message-----
> >> From: David Rees [mailto:drees@greenhydrant.com]
> >> 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: tomcat-user-unsubscribe@jakarta.apache.org
> >> For additional commands, e-mail:
> tomcat-user-help@jakarta.apache.org
> >>
> >
> >
> >__
> >    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: tomcat-user-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
>
>
> 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: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org


Mime
View raw message