[jboss-jira] [JBoss JIRA] (AS7-5508) Activation of OSGi causes missing/unsatisfied service dependencies

[Thomas Diesler (JIRA)]

     [ https://issues.jboss.org/browse/AS7-5508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Diesler reassigned AS7-5508:
-----------------------------------

    Assignee: David Lloyd  (was: Thomas Diesler)


David, I'd like to get this rolling. It seems to be a general enough problem. Perhaps you can get back to me when this moves into focus. Cheers
                
> Activation of OSGi causes missing/unsatisfied service dependencies
> ------------------------------------------------------------------
>
>                 Key: AS7-5508
>                 URL: https://issues.jboss.org/browse/AS7-5508
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: OSGi, Server
>            Reporter: Thomas Diesler
>            Assignee: David Lloyd
>             Fix For: 7.2.0.Alpha1
>
>
> Activating OSGi through management op (console/cli) will get
> {code}
> 13:15:06,192 INFO  [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011006: OSGi Framework - 2.0.0.CR21
> 13:15:06,561 INFO  [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011001: Bundle installed: org.apache.felix.configadmin:1.2.8
> 13:15:06,562 INFO  [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011001: Bundle installed: org.apache.felix.log:1.0.0
> 13:15:06,563 INFO  [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011001: Bundle installed: jboss-osgi-logging:1.0.0
> 13:15:06,565 INFO  [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011001: Bundle installed: jboss-as-osgi-configadmin:7.2.0.Alpha1-SNAPSHOT
> 13:15:06,739 INFO  [org.jboss.as.controller] (MSC service thread 1-2) JBAS014774: Service status report
> JBAS014775:    New missing/unsatisfied dependencies:
>       service jbosgi.integration.BootstrapBundles.COMPLETE (missing) dependents: [service jbosgi.internal.framework.INIT, service jbosgi.integration.PersistentBundles.INSTALL, service jboss.osgi.as.module.registration] 
>       service jbosgi.integration.PersistentBundles.COMPLETE (missing) dependents: [service jbosgi.internal.framework.INIT] 
> 13:15:06,758 INFO  [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011011: Starting bundles for start level: 1
> 13:15:06,778 INFO  [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011002: Bundle started: jboss-osgi-logging:1.0.0
> 13:15:06,791 INFO  [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011002: Bundle started: jboss-as-osgi-configadmin:7.2.0.Alpha1-SNAPSHOT
> 13:15:06,816 INFO  [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011002: Bundle started: org.apache.felix.log:1.0.0
> 13:15:06,864 INFO  [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011002: Bundle started: org.apache.felix.configadmin:1.2.8
> 13:15:06,867 INFO  [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011000: OSGi Framework started
> 13:15:06,887 INFO  [org.jboss.web] (MSC service thread 1-1) JBAS018210: Register web context: /httpservice
> 13:15:06,905 INFO  [org.jboss.as.controller] (MSC service thread 1-3) JBAS014774: Service status report
> JBAS014776:    Newly corrected services:
>       service jbosgi.integration.BootstrapBundles.COMPLETE (no longer required)
>       service jbosgi.integration.PersistentBundles.COMPLETE (no longer required)
> {code}
> This is related to AS7-5365 but now easily re-producable in master. More background is given here
> https://community.jboss.org/wiki/OSGiSubsystemActivationProcess

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira