You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@aries.apache.org by "Siano, Stephan" <st...@sap.com> on 2013/08/30 08:32:22 UTC
Strange startup behaviour for subsystems
Hi,
I encounter some strange issues with the aries subsystem lifecycle.
1. If I stop the container (or only the subsystem.core bundle) any newly installed subsystem will get id 1 afterwards, even if another subsystem with that id already exists. I guess this is clearly a bug and I opened https://issues.apache.org/jira/browse/ARIES-1109 for that.
2. If I install and start a subsystem containing any bundles the bundles and the subsystem are there and in active state. If I now stop the OSGi container and start it again, the bundles and subsystems are still there, the subsystems are also in active state, but the bundles contained in the subsystems are only in resolved state. If I stop and start the subsystem the bundles are back to active state. (btw.: If I just stop an start the subsystem.core bundle the bundles contained in the subsystem will go to resolved and then back to active state.) Maybe this is somewhat related to the way equinox preserves states. Should I open another jira bug for this?
Best regards
Stephan
Re: Strange startup behaviour for subsystems
Posted by Roger Stocker <ro...@stocker.nu>.
Hello Stephan
My boyfriend Roger Stocker is dead. I'm sorry for that bad News.
Kindly regards
Maike Marx
Am 30.08.2013 um 08:32 schrieb "Siano, Stephan" <st...@sap.com>:
> Hi,
>
> I encounter some strange issues with the aries subsystem lifecycle.
> 1. If I stop the container (or only the subsystem.core bundle) any newly installed subsystem will get id 1 afterwards, even if another subsystem with that id already exists. I guess this is clearly a bug and I opened https://issues.apache.org/jira/browse/ARIES-1109 for that.
> 2. If I install and start a subsystem containing any bundles the bundles and the subsystem are there and in active state. If I now stop the OSGi container and start it again, the bundles and subsystems are still there, the subsystems are also in active state, but the bundles contained in the subsystems are only in resolved state. If I stop and start the subsystem the bundles are back to active state. (btw.: If I just stop an start the subsystem.core bundle the bundles contained in the subsystem will go to resolved and then back to active state.) Maybe this is somewhat related to the way equinox preserves states. Should I open another jira bug for this?
>
> Best regards
> Stephan