tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shapira, Yoav" <>
Subject RE: Memory Leak with static content
Date Mon, 15 Sep 2003 17:40:19 GMT

Run your app with a  profiler and a stress tool and see when and where
memory is allocated.

Yoav Shapira
Millennium ChemInformatics

>-----Original Message-----
>From: Seth Newton []
>Sent: Monday, September 15, 2003 1:34 PM
>To: Tomcat Users List
>Subject: Re: Memory Leak with static content
>Updates to this issue....
>-I'm not sure if it's the OS, but I've never seen this happen before on
>other Solaris installs.  What would I look at to determine if it's the
>The way that question is phrased makes it difficult for me to
>understand what you mean. Can you be more specific?
>-It did take up memory until Tomcat would no longer serve pages.  Users
>would try to see their sites and just get a blank white screen until
>request timed out.  I haven't let it time go incrementally since I've
>upgraded Tomcat or the jdk, however, I may let it stall out if I get
>-I upgraded to 1.4.2 and still the memory increases.
>-Yes, I'm closing all streams in the email class.  Also, this
>code has been used successfully across platforms and across java
>about 3 years now.
>Anymore input is greatly appreciated.
>----- Original Message -----
>From: "Nikolaos Giannopoulos" <>
>To: "Tomcat Users List" <>
>Sent: Friday, September 12, 2003 6:04 PM
>Subject: RE: Memory Leak with static content
>> Seth,
>> Have you tried JDK 1.4.2?  1.4.0 has been known to have a memory leak
>> StringBuffer implementation w.r.t. re-using StringBuffers but you
>> that your only serving static content so this may not be it.
>> However, I believe that I read that something like 2000 bugs have
>> in 1.4.2 (if my memory serves me well).  We have have no visible
>> running tomcat 4.1.12/18 stand alone w/ 1.4.2 on Solaris 8 on 4 boxes
>> JSPs - just servlets and static content).
>> Please reply back if this works or does not work for you - we are
>> upgrading our Tomcat instances in the near future.
>> HTH.
>> --Nikolaos
>> > -----Original Message-----
>> > From: Seth Newton []
>> > Sent: Friday, September 12, 2003 4:58 PM
>> > To:
>> > Subject: Memory Leak with static content
>> >
>> >
>> > All,
>> >
>> > OS: Sparc-Solaris 9
>> > JDK: 1.4.0_02
>> > Tomcat: 4.1.27
>> >
>> > Problem:
>> > I start tomcat and it takes up about 45MB of RAM.  I wrote a
>> > script to email me every ten minutes the amount of memory it's
>> > taking up.  The results are showing me that it gains about 1MB
>> > every 10 minutes or so (on average).  If I let it go, it will
>> > grow until it runs out of memory.  Right now, I have a script to
>> > restart tomcat after the memory is too high.  This is a bad
>> > solution.  I've looked at a LOT of people's suggestions from
>> > other threads, and I have tried the following:
>> >
>> > -Use jikes
>> > -Set development to false in web.xml
>> > -Increase the heap sizes
>> > -set fork to true in web.xml
>> >
>> > Other Info:
>> > -I'm using Tomcat to feed about 6 sites with static content.  I
>> > have one jsp page that handles all of our forms, and all that
>> > does is capture the <input> and send it to an email address.  It
>> > is the only code I have anywhere.  This jsp page is not causing
>> > the memory leak.
>> > -I had the same problem with 4.1.17, and was hoping that an
>> > update would help, but it didn't.
>> > -This is an incremental increase, and doesn't seem to have much
>> > to do with traffic patterns or how much I use my one jsp page.
>> >
>> > Any suggestions would be great.
>> > -Seth.
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:
>To unsubscribe, e-mail:
>For additional commands, e-mail:

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.

View raw message