Subject: memory leak on context reload or stop/start? [was Re: tracking
memory usage over time]
Just to followup, we have found a few things that were causing this
leak, two that were particular to our setup, but the third seems to be
a Tomcat problem (4.1.20 with Jasper2):
1) log4j was eating up
- Original Message -
From: Aditya [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Sent: Friday, March 14, 2003 10:27 AM
Subject: memory leak on context reload or stop/start? [was Re: tracking
memory usage over time]
Just to followup, we have found a few things that were
, February 26, 2003 6:55 AM
To: Tomcat Developers List
Subject: Re: tracking memory usage over time
Glenn,
several months ago you had posted a URL to a document (at
kinetic.more.net if I remember correctly) where you talked about
having to restart your production Tomcat(s) every 4 weeks or so due
Glenn,
several months ago you had posted a URL to a document (at
kinetic.more.net if I remember correctly) where you talked about
having to restart your production Tomcat(s) every 4 weeks or so due to
Heap exhaustion. Is that still the case? If so what causes the heap
exhaustion?
We've looked
Aditya wrote:
Glenn,
several months ago you had posted a URL to a document (at
kinetic.more.net if I remember correctly) where you talked about
having to restart your production Tomcat(s) every 4 weeks or so due to
Heap exhaustion. Is that still the case? If so what causes the heap
exhaustion?
I
Hi Aditya,
there is product of Borland OptimizeitT Suite 5 which makes performance
management for JavaT easier .It dramatically improvs application performance
and supporting the development of fast, scalable, and reliable applications.
Optimizeit Suite offers another innovative
An easier way to measure memory usage in production is to start the JVM which
runs Tomcat with the arg -verbose:gc, this will print information
to stdout about each garbage collection and the memory used.
I doubt if the memory leak is in Tomcat itself. The best way to find
the memory leak in
Is there any particular reason the pages are
recompiled frequently? If you're using tomcat 4.1.12
or newer, it should use Ant to compile the pages,
which should get around the issue of memory leak due
to page compilation.
peter
--- Aditya [EMAIL PROTECTED] wrote:
I have the following JSP
On Fri, 14 Feb 2003 06:45:26 -0600, Glenn Nielsen [EMAIL PROTECTED] said:
An easier way to measure memory usage in production is to start the
JVM which runs Tomcat with the arg -verbose:gc, this will print
information to stdout about each garbage collection and the memory
used.
thank you,
