[ARIES-1398] Aries Subsystem implementation is start-order dependent

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: subsystem-2.0.2
• Component/s: Subsystem
• Assignee: Unassigned
• Reporter: David Bosschaert
• Created: 09/Sep/15 08:23
• Updated: 07/Oct/15 16:06
• Resolved: 28/Sep/15 13:35

Description

From an email thread by Paul F Frazer: https://mail-archives.apache.org/mod_mbox/aries-user/201509.mbox/browser

When the Aries Subsystem implementation is started in a certain order the synthesized org.osgi.service.subsystem.region.context.0 bundle is not created.

While the original bug was reported on the Raspberry Pi, this can also be reproduced on an ordinary laptop. For example by starting the bundles in the following order:

START LEVEL 1
   ID|State      |Level|Name
    0|Active     |    0|System Bundle (5.2.0)
    1|Active     |    1|Apache Felix Bundle Repository (2.0.4)
    2|Active     |    1|Apache Felix Gogo Command (0.14.0)
    3|Active     |    1|Apache Felix Gogo Runtime (0.16.2)
    4|Active     |    1|Apache Felix Gogo Shell (0.10.0)
    5|Active     |    1|Apache Felix Configuration Admin Service (1.8.6)
    6|Active     |    1|Apache Felix Coordinator Service (1.0.0)
    7|Active     |    1|osgi.cmpn (5.0.0.201305092017)
    8|Active     |    1|slf4j-api (1.7.12)
    9|Active     |    1|Region Digraph (1.1.0.v20120522-1841)
   10|Active     |    1|Apache Aries Subsystem Core (2.0.2)
   11|Resolved   |    1|slf4j-simple (1.7.12)
   12|Active     |    1|Apache Aries Util (1.1.1)
   13|Active     |    1|Apache Aries Subsystem API (2.0.2)

As you can see the synthesized bundle does not appear.

Issue Links

• is blocked by: FELIX-5049 Resolver does not choose the revision with the lowest bundle ID