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 2018/02/16 08:08:00 UTC

[jira] [Closed] (ARIES-1031) BlueprintExtender unnecassarily shutting down

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

Guillaume Nodet closed ARIES-1031.
----------------------------------
    Resolution: Fixed

Composite bundles have disappeared now.

> BlueprintExtender unnecassarily shutting down
> ---------------------------------------------
>
>                 Key: ARIES-1031
>                 URL: https://issues.apache.org/jira/browse/ARIES-1031
>             Project: Aries
>          Issue Type: Bug
>          Components: Blueprint
>            Reporter: Chris Wilkinson
>            Priority: Major
>
> Changes introduced in ARIES-1004 caused early shutdown of the blueprintextender when CompositeBundles exist in the system.
> CompositeBundles have their own system bundles which have an id of 0. Therefore we can have a system where there are multiple bundles with id=0. The code added in 1004 shuts down the extender when a bundle with id=0 is stopped. Therefore we shut down everything when we stopped a composite.
> I will update the check to compare the stopping bundle with the actual system bundle.



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