-
Bug
-
Resolution: Done
-
Major
-
None
-
None
On OSGi subsystem activation the server may report missing/unsatisfied dependencies.
However, that service is in fact installed and active. Otherwise, the framework would not initialize let alone start.
12:48:39,952 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011004: JBossOSGi Framework Core - 1.3.0.CR9 12:48:41,036 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011009: Starting bundles for start level: 1 12:48:41,039 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011001: Bundle started: osgi.enterprise:4.2.0.201003190513 12:48:41,041 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011001: Bundle started: javax.servlet.api:2.5.0.Final 12:48:41,060 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011001: Bundle started: jboss-osgi-logging:1.0.0 12:48:41,072 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011001: Bundle started: jboss-as-osgi-configadmin:7.1.2.Final-SNAPSHOT 12:48:41,074 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011000: OSGi Framework started 12:48:41,352 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "foo" 12:48:41,353 INFO [org.jboss.as.controller] (management-handler-thread - 2) JBAS014774: Service status report JBAS014775: New missing/unsatisfied dependencies: service jbosgi.integration.AutoInstallHandler.COMPLETE (missing) dependents: [service jbosgi.integration.PersistentBundlesHandler, service jbosgi.framework.INIT]
A possible source of the issue is that the service in question (jbosgi.integration.AutoInstallHandler.COMPLETE) gets added by a listener and is not part of the normal service dependency chain.
- is blocked by
-
-
- Resolved
-
