[jira] [Closed] (ARIES-1891) Memory Leak in aries-jpa-support

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Closed] (ARIES-1891) Memory Leak in aries-jpa-support

JIRA jira@apache.org

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

Daniel Estermann closed ARIES-1891.
-----------------------------------
    Resolution: Fixed

The memory leak is fixed in https://github.com/apache/aries-jpa/commit/8f46ae5c58e90832ab8886ab6f5d7c7d9f7fada2

> Memory Leak in aries-jpa-support
> --------------------------------
>
>                 Key: ARIES-1891
>                 URL: https://issues.apache.org/jira/browse/ARIES-1891
>             Project: Aries
>          Issue Type: Bug
>          Components: JPA
>    Affects Versions: jpa-2.7.1
>            Reporter: Daniel Estermann
>            Priority: Critical
>             Fix For: jpa-2.7.2
>
>
> The fix for ARIES-1783 has a memory leak. The method org.apache.aries.jpa.supplier.EmSupplier.get() is called every time when a method on EntityManager is called. And every time a ServiceReference to a TransactionManager gets created. But it doesn't get deleted. So we have as many ServiceReferences in the memory as calls on EntityManager.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)