Tomcat Developers List
>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
- 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 follow
> On Tue, 25 Feb 2003 22:08:41 -0600, Glenn Nielsen <[EMAIL PROTECTED]> said:
> Does the increase in memory usage correlate with an increased number
> of connectors due to a spike in request volume?
There does not seem to be a correlation between a request spike and
un-gc'able heap usage. I'm usi
, 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 to
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 t
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 hig
> 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 y
> On Fri, 14 Feb 2003 05:14:33 -0800 (PST), Peter Lin <[EMAIL PROTECTED]> said:
> 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 co
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 t
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 your
Sent: Friday, February 14, 2003 10:38 AM
To: [EMAIL PROTECTED]
Subject: tracking memory usage over time
I have the following JSP that I hit every 5 minutes and stuff the
returned values into a RRD (www.rrdtool.org) to measure the memory
(heap I presume) consumption of Tomcat over time. Is there a
I have the following JSP that I hit every 5 minutes and stuff the
returned values into a RRD (www.rrdtool.org) to measure the memory
(heap I presume) consumption of Tomcat over time. Is there a "better"
way, short of using JMX in the newer Tomcat builds, of doing this?
<%@ page language="java" %>
12 matches
Mail list logo
