David Bosschaert created ARIES-1398:
---------------------------------------
Summary: Aries Subsystem implementation is start-order dependent
Key: ARIES-1398
URL: https://issues.apache.org/jira/browse/ARIES-1398
Project: Aries
Issue Type: Bug
Components: Subsystem
Affects Versions: subsystem-2.0.2
Reporter: David Bosschaert
Attachments: nowork.txt, works.txt
>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:
{code}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)
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)
14|Active | 1|Apache Aries Subsystem Core (2.0.2)
{code}
As you can see the synthesized bundle does not appear.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
