[jira] [Resolved] (DELTASPIKE-1392) Repositories seem to prevent Garbage Collection from Weblogic

["Thomas Andraschko (Jira)" <ji...@apache.org>]

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

Thomas Andraschko resolved DELTASPIKE-1392.
-------------------------------------------
    Resolution: Duplicate

https://issues.apache.org/jira/browse/DELTASPIKE-1398

> Repositories seem to prevent Garbage Collection from Weblogic
> -------------------------------------------------------------
>
>                 Key: DELTASPIKE-1392
>                 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1392
>             Project: DeltaSpike
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Data-Module
>    Affects Versions: 1.8.0
>         Environment: Oracle 12c
> Weblogic 12.2.1-3-0
> Java EE 7
> Java SE 8
> Deltaspike 1.8.0
>            Reporter: THEODOROS CHAIKALIS
>            Priority: Major
>         Attachments: Heap_walker_Incoming_References.html, Heap_walker_Incoming_References_2.html
>
>
> During my effort to detect possible memory leaks in our application i found a strange behavior of Deltaspike regarding the handling of Repositories.
> Specifically, after the *undeployment* and {color:#de350b}*deletion*{color} of a Java EE 7 war, Weblogic still holds all references to proxy EJBs that created before. 
> Attached you will find the Heap dump for an EJB Service where if you trace the source you will end up in a 
> {{*bmpSingleton* of class org.apache.deltaspike.core.api.provider.BeanManagerProvider.}}
>  
> Am i missing some critical configuration for Weblogic?
> I already have declared 
> {{globalAlternatives.org.apache.deltaspike.jpa.spi.transaction.TransactionStrategy=org.apache.deltaspike.jpa.impl.transaction.ContainerManagedTransactionStrategy}}
> inside apache-deltaspike.properties.
>  
> Thank you
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)