tomee-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim McConnell (JIRA)" <j...@apache.org>
Subject [jira] Updated: (OPENEJB-622) EntityEJBObjectHandler memory leak
Date Thu, 02 Aug 2007 08:00:53 GMT

     [ https://issues.apache.org/jira/browse/OPENEJB-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tim McConnell updated OPENEJB-622:
----------------------------------


It appears that the EntityEJbObjectHandler memory leak has been fixed with R561163. The before
and after snapshots are availalbe here: 

http://people.apache.org/~mcconne/08-02-2007/

There is still a memory leak somewhere as I can still force an OOM condition if I do enough
iterations of the scenario that Kevan listed. 


> EntityEJBObjectHandler memory leak
> ----------------------------------
>
>                 Key: OPENEJB-622
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-622
>             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: http://people.apache.org/~kevan/EntityEjbObjectHandlerMemoryLeak.html
> 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.


Mime
View raw message