You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@aries.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2017/03/20 13:22:41 UTC

[jira] [Resolved] (ARIES-1634) BlueprintContainer are leaked when destroyed

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

Guillaume Nodet resolved ARIES-1634.
------------------------------------
       Resolution: Fixed
    Fix Version/s: blueprint-core-1.8.1

> BlueprintContainer are leaked when destroyed
> --------------------------------------------
>
>                 Key: ARIES-1634
>                 URL: https://issues.apache.org/jira/browse/ARIES-1634
>             Project: Aries
>          Issue Type: Bug
>          Components: Blueprint
>    Affects Versions: blueprint-core-1.4.2
>         Environment: OSx
>            Reporter: Alexis de Talhouët
>            Assignee: Guillaume Nodet
>              Labels: easyfix
>             Fix For: blueprint-core-1.8.1
>
>
> When the BlueprintContainer is #destroy(), it is not unregistered from the OSGi registry hence is retained in the memory.
> But when the BlueprintContainer is #quiesce() it is correctly unregistered from the OSGi registry.
> The workaround it to first #quiesce() the container, then #destroy() it, so no service is retaining it, and it can be GC.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)