tomee-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim McConnell (JIRA)" <>
Subject [jira] Updated: (OPENEJB-622) EntityEJBObjectHandler memory leak
Date Wed, 01 Aug 2007 17:49:52 GMT


Tim McConnell updated OPENEJB-622:

Hi David, I've captured some "Before" the fix snapshots of the heap with JProbe just to ensure
that your fix eliminates the leak. They are at:

The scenario I'm using (that hopefully is exactly the same as Kevan was using) is:
	1 - Logon Geronimo 
	2 - Deploy DT
	3 - Populate tables
	4 - Restart server
	5 - Configure DT for EJB3
	6 - Start profiling
	5 - Login DT
	6 - Logoff DT
	7 - Undeploy
                     8 - Stop profiling

So you can see in the before snapshot that BaseEjbProxyHandler has accumulated almost 2mb
of storage on the heap at the end of this scenario..... I'm profiling the "After" fix scenario
now and will post the results shortly to the same URL. Thanks

> EntityEJBObjectHandler memory leak
> ----------------------------------
>                 Key: OPENEJB-622
>                 URL:
>             Project: OpenEJB
>          Issue Type: Bug
>    Affects Versions: 3.0
>            Reporter: Kevan Miller
>            Assignee: David Blevins
>            Priority: Critical
>             Fix For: 3.0
> I'm seeing Geronimo ClassLoader memory leaks in deploy, use, undeploy scenarios using
Daytrader. When Daytrader is configured to run in EJB mode, ClassLoaders are not being GC'ed.

> A sample reference pattern from GC roots to the ClassLoader is here:
> BaseEjbProxyHandler.liveHandleRegistry is maintaining sets of BaseEjbProxyHandlers. References
to EntityEJb handlers are never being cleared.
> I never see EjbHomeProxyHandler._invoke() called with a REMOVE operation (which looks
like it would drive the necessary cleanup).

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message