[jira] Resolved: (OPENEJB-622) EntityEJBObjectHandler memory leak

["David Blevins (JIRA)" <ji...@apache.org>]

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

David Blevins resolved OPENEJB-622.
-----------------------------------

    Resolution: Fixed

Committed a change:
$ svn ci container 
Sending        container/openejb-core/src/main/java/org/apache/openejb/core/ivm/BaseEjbProxyHandler.java
Transmitting file data .
Committed revision 561163.

... that moves the registry into the deploymentinfo (which is destroyed on undeploy) so the related refs should die.

Give this fix a try and if this leak is gone, close the issue.

> 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.