[
https://issues.apache.org/jira/browse/ARIES-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Hughes updated ARIES-696:
--------------------------------
Fix Version/s: blueprint.itests-0.4
blueprint.core-0.4
blueprint uber bundle 0.4
> Blueprint container can appear to loose memory when frequently restarted
> ------------------------------------------------------------------------
>
> Key: ARIES-696
> URL: https://issues.apache.org/jira/browse/ARIES-696
> Project: Aries
> Issue Type: Bug
> Components: Blueprint
> Reporter: Valentin Mahrwald
> Priority: Minor
> Fix For: blueprint uber bundle 0.4, blueprint.core-0.4,
> blueprint.itests-0.4
>
>
> This is not a memory leak per se in that the memory claimed will eventually
> be freed. However, in some situations that only occurs after the JVM has
> actually run out of memory :)
> The problem is that ScheduledExecutors by default hang on to scheduled
> futures *even* if they have been cancelled. Which means whole Blueprint
> containers can be kept alive after they have been destroyed ...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
