Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@geronimo.apache.org
Received-SPF: pass (nike.apache.org: domain of kevan.miller@gmail.com
 designates 209.85.160.182 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=content-type:mime-version:subject:from:in-reply-to:date
         :content-transfer-encoding:message-id:references:to:x-mailer;
        b=bs1xbtO7l5P4ifm927tH0suKohqXQS1SXgqFRCCjYEIDR1/E22mIGZNcCNPT3cW1dW
         BM7ZkTDb9RO8YwbysR8evsND6bAiKDn8+q7H+B1NjG2y21yZvpgXyU7zrh/7WDsKVwqA
         K1LqCevnreTboEgAqEO3ikt/guelTLWXX1/W4=
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1081)
Subject: Re: Memory leak using Geronimo 2.1.4? Having 116760 instances of
 LifecycleEvent
From: Kevan Miller <kevan.miller@gmail.com>
In-Reply-To: <1285948748971-1615458.post@n3.nabble.com>
Date: Fri, 1 Oct 2010 13:01:08 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F9638542-62B4-457F-9DE6-D8111D071741@gmail.com>
References: <1285948748971-1615458.post@n3.nabble.com>
To: user@geronimo.apache.org


On Oct 1, 2010, at 11:59 AM, boes wrote:

> I need help. How can I debug this problem?

You've got a good start -- a heap dump that shows a number of =
LifecycleEvent and Container instances. They should definitely be =
investigated.

I've found YourKit to be very helpful in analyzing heapdumps. I've never =
used jhat, but have used Eclipse MAT, which should do the job, also...=20=


Using the tool, you want to identify the GC roots of the LifeCycleEvent =
and/or Container objects. By GC Root, I mean the chain of references =
which are preventing the objects from being GC'ed.=20

> Is it a Geronimo or a Tomcat
> issue? What part of Geronimo or Tomcat generates all these =
LifecycleEvents?
> Can it be a result of some programming errors in our application? I =
looked
> in the heap dump for classes from our own application and the first in =
the
> list only has 208 instances.

I don't recall seeing a similar problem. So, can't predict where the =
problem is, yet. What are you doing with the server. Are you =
deploying/redeploying many applications? Are you stopping/starting =
modules?

LIfecycleEvents get generated when Tomcat components change state =
(start, stop, etc). I think I recall a timer-based lifecycle event, =
also. =20

Given the number of Container[] objects, I would say they must be =
Container events... If you can inspect the contents of the =
LifeCycleEvents, there should be a type field which will tell you what =
type of events are being generated.

--kevan=