You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Valentin Mahrwald (JIRA)" <ji...@apache.org> on 2010/06/25 18:00:54 UTC
[jira] Created: (ARIES-342) Blueprint leaking memory in
multi-framework environment
Blueprint leaking memory in multi-framework environment
-------------------------------------------------------
Key: ARIES-342
URL: https://issues.apache.org/jira/browse/ARIES-342
Project: Aries
Issue Type: Bug
Components: Blueprint
Affects Versions: 0.1
Reporter: Valentin Mahrwald
Assignee: Valentin Mahrwald
Fix For: 0.2
With the current AriesBundleTrackerCustomizer that allows one Blueprint container to track composite sub-frameworks, the blueprint extender class leaks memory in that it never disposes of existing blueprint containers. The reason for this behaviour is that the bundle tracker to the composite bundle is deregistered on stopping, which is before any bundles inside the composite bundle are stopped.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (ARIES-342) Blueprint leaking memory in
multi-framework environment
Posted by "Valentin Mahrwald (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Valentin Mahrwald resolved ARIES-342.
-------------------------------------
Resolution: Fixed
Fix committed in #958509.
> Blueprint leaking memory in multi-framework environment
> -------------------------------------------------------
>
> Key: ARIES-342
> URL: https://issues.apache.org/jira/browse/ARIES-342
> Project: Aries
> Issue Type: Bug
> Components: Blueprint
> Affects Versions: 0.1
> Reporter: Valentin Mahrwald
> Assignee: Valentin Mahrwald
> Fix For: 0.2
>
>
> With the current AriesBundleTrackerCustomizer that allows one Blueprint container to track composite sub-frameworks, the blueprint extender class leaks memory in that it never disposes of existing blueprint containers. The reason for this behaviour is that the bundle tracker to the composite bundle is deregistered on stopping, which is before any bundles inside the composite bundle are stopped.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.