Re: Finding a Memory Leak in a Web Application
At 11:43 PM 27/06/01, you wrote: I think my application is leaking. Over time the size of the Java process grows but never shrinks back down. I'm not sure of the best way to find the leak. I can't afford expensive profiling tools like OptimizeIt, etc... You can download an evaluation version of OptimizeIt and JProbe - not the ideal solution, I agree, but you might find that the 30 day usage is sufficient... It may be something as simple as a design flaw on my part... Here's my design: requests come into a servlet which creates vectors of objects from database data. These vectors are stored in the request scope and then I forward to a JSP page where the results are displayed from the Vectors. I assumed (incorrectly?) that since they were in the request scope they would be garbage collected after the request was over (which is when the page has been sent to the user, right?). Is this not the case? Any help/suggestions anyone has would be great! Have you tried manually wiping the Vector (myVector.clear()) at the end of the jsp page after using the data? Does this fix/confirm the cause of the problem? Hunter -- * Jim Cheesman * Trabajo: [EMAIL PROTECTED] - (34)(91) 724 9200 x 2360 Profanity sucks.
RE: Aw: Finding a Memory Leak in a Web Application
Try using HAT (Heap Analysis Tool), you can download it from Sun. It allows you to take snap shots of the heap at run time and exports it as HTML pages.. letting you see just how many objects, and of what types have been created. - Chris. Brainbench MVP Java2 -Original Message- From: Hunter Hillegas [mailto:[EMAIL PROTECTED]] Sent: 27 June 2001 23:04 To: Tomcat User List Subject: Re: Aw: Finding a Memory Leak in a Web Application Whoops. Forgot to give my info: Tomcat 3.2.2 on JDK1.3.1 / Red Hat Linux 6.0 with updated libs. Running Apache 1.3.19 in front, using APJ12. From: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Date: Wed, 27 Jun 2001 23:50:55 +0200 (CEST) To: [EMAIL PROTECTED] [EMAIL PROTECTED] Subject: Aw: Finding a Memory Leak in a Web Application Simple question: What JDK version are you using ?` I had similiar problems with 1.2.x After upgrading, the were gone (an new appeared, quite nomal with java i think :-) I think my application is leaking. Over time the size of the Java process grows but never shrinks back down. I'm not sure of the best way to find the leak. I can't afford expensive profiling tools like OptimizeIt, etc... It may be something as simple as a design flaw on my part... Here's my design: requests come into a servlet which creates vectors of objects from database data. These vectors are stored in the request scope and then I forward to a JSP page where the results are displayed from the Vectors. I assumed (incorrectly?) that since they were in the request scope they would be garbage collected after the request was over (which is when the page has been sent to the user, right?). Is this not the case? Any help/suggestions anyone has would be great! Hunter -- NOTICE: The information contained in this electronic mail transmission is intended by Convergys Corporation for the use of the named individual or entity to which it is directed and may contain information that is privileged or otherwise confidential. If you have received this electronic mail transmission in error, please delete it from your system without copying or forwarding it, and notify the sender of the error by reply email or by telephone (collect), so that the sender's address records can be corrected.
Finding a Memory Leak in a Web Application
I think my application is leaking. Over time the size of the Java process grows but never shrinks back down. I'm not sure of the best way to find the leak. I can't afford expensive profiling tools like OptimizeIt, etc... It may be something as simple as a design flaw on my part... Here's my design: requests come into a servlet which creates vectors of objects from database data. These vectors are stored in the request scope and then I forward to a JSP page where the results are displayed from the Vectors. I assumed (incorrectly?) that since they were in the request scope they would be garbage collected after the request was over (which is when the page has been sent to the user, right?). Is this not the case? Any help/suggestions anyone has would be great! Hunter
Aw: Finding a Memory Leak in a Web Application
- Original Nachricht Von: Hunter Hillegas [EMAIL PROTECTED] An: Tomcat User List [EMAIL PROTECTED] Datum: 27.06.01 23:43 Betreff: Finding a Memory Leak in a Web Application I think my application is leaking. Over time the size of the Java process grows but never shrinks back down. Simple question: What JDK version are you using ?` I had similiar problems with 1.2.x After upgrading, the were gone (an new appeared, quite nomal with java i think :-) Bye, Oli Eales germany.net Technik Tel: +49-69-63397411
Re: Aw: Finding a Memory Leak in a Web Application
Whoops. Forgot to give my info: Tomcat 3.2.2 on JDK1.3.1 / Red Hat Linux 6.0 with updated libs. Running Apache 1.3.19 in front, using APJ12. From: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Date: Wed, 27 Jun 2001 23:50:55 +0200 (CEST) To: [EMAIL PROTECTED] [EMAIL PROTECTED] Subject: Aw: Finding a Memory Leak in a Web Application Simple question: What JDK version are you using ?` I had similiar problems with 1.2.x After upgrading, the were gone (an new appeared, quite nomal with java i think :-)
