Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: tomcat-dev@jakarta.apache.org
Date: Fri, 12 Oct 2001 10:21:59 -0500
Message-ID: <000c01c15331$a2fe4400$9500000a@infinitecampus.org>
From: "David Frankson" <dfrankson@qwest.net>
To: tomcat-dev@jakarta.apache.org
Subject: memory leak?
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0009_01C15307.B9F740F0"

------=_NextPart_000_0009_01C15307.B9F740F0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

    I've been using Tomcat 3.2.3 in a production environment for a =
couple months without a problem.  Last week I added a new feature and =
now the tomcat process will consume memory until it reaches the -Xmx512 =
size I have set. =20

I ran the same webapp under Tomcat 4.0 and I see the same behavior.   =
However, I ran the same webapp under resin 2.0.2 and there is no =
evidence of a memory leak.=20

I downloaded JProbe to take a look at the heap, and the most interesting =
thing I found was that there was a 33Mb byte[] referenced by =
HttpResponseAdapter.  I didn't see any objects from my application code =
that weren't supposed to be there.

Has anyone encountered something like this?  What in my application can =
cause Tomcat to hold onto memory and never release it? =20

Dave Frankson

------=_NextPart_000_0009_01C15307.B9F740F0--