I've just overcome this situation too, and would say my code now has 75%
more explicit
flush(), close(), and x=null statements, plus make sure you're using
hotspot, as gc on hotspot seems to be 1,000,000,000 times more effective
I *know* what you are going through, don't give up youwill win in the end.
in my case I ran out of memory after about 2-300,000 hits. now it sits
happily on a test set-up at 19-24% memory use, 84% cpu load serving 12
clients 2 hits per second each, day in day out no complaints.
d.
;-)
> -----Original Message-----
> From: Randy Layman [mailto:[EMAIL PROTECTED]]
> Sent: Monday, April 16, 2001 6:50 PM
> To: [EMAIL PROTECTED]
> Subject: RE: java.lang.OutOfMemoryError... O happy day.
>
>
>
> Tomcat itself doesn't leak any memory as far as our systems
> indicate. One thing to look at might be session usage - has the orginial
> developer made the session never timeout (which means that the memory used
> in it will never be recollected) or jave exceptionally long
> timeouts? Also,
> since you can't connect to the database, I would look at that
> portion of the
> code, possibly keeping connections open until you use all the database
> server/license supports?
>
> As you probably know, you need to look at objects that grow without
> being garbage collected (static variables are often times problems,
> especially Collections (maps, lists, etc)) as well as keeping open IO
> streams with very large buffers and not flushing them at points of
> inactivity.
>
> Randy
>
> > -----Original Message-----
> > From: Daniel Wintschel [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, April 16, 2001 2:14 PM
> > To: [EMAIL PROTECTED]
> > Subject: java.lang.OutOfMemoryError... O happy day.
> >
> >
> > Hey there.
> >
> > I just took over a project that is running on Solaris 2.6 and
> > an Apache
> > 1.3.12/Tomcat 3.2.1 install.
> >
> > After about three days of the server being up, it slows to a
> > crawl and dies
> > a wonderful death spewing forth Internal Server Errors and a wonderful
> > inability to connect to any databases. (Namely repeated
> > java.lang.OutOfMemoryError's)
> >
> > I am wondering if there are any known issues of memory leaks in this
> > distribution of Tomcat, or if my most probable solution to
> > the problem would
> > be to read through all of the previous developers code to
> > find out where it
> > sucks and needs to get fixed.
> >
> > The Frustrated Code Maintainer.
> > -daniel
> >
> > ___________________________________________
> > ...what is of value is never the habits and skills acquired
> > from practice, but the understanding that results from
> > consciously undertaken struggles...
> > ___________________________________________
> > Daniel Wintschel
> > Java/Web Developer
> >
> > Tantalus Communications Inc.
> > 500-1122 Mainland Street
> > Vancouver BC V6B 5L1
> >
> > eMaiL: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
> > diReCt: 604.782.2713
> > MaiN: 604.609.0700
> > faX: 604.609.0705
> >
> > http://www.tantalus.com <http://www.tantalus.com>
> > "When eBusiness Experience Counts."
> >
> >
