[jboss-jira] [JBoss JIRA] (AS7-4603) Controller incorrectly reports missing service dependencies

[Thomas Diesler (JIRA)]

    [ https://issues.jboss.org/browse/AS7-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12690330#comment-12690330 ] 

Thomas Diesler commented on AS7-4603:
-------------------------------------

There might be a conceptual flaw in "overall stability check will be complete and the "Service status report" will be printed". 

If check and print was atomic it'd not be possible to have missing dependencies be reported that are in fact available and active.

I suspect that stability is detected (i.e. FRAMEWORK_INIT at ON_DEMAND and AUTOINSTALL_COMPLETE not there) then stuff still happens then the report is printed with stale data i.e. it reports out of date service states 

If I look at the logs AUTOINSTALL_COMPLETE becomes ACTIVE, which is a requirement for FRAMEWORK_INIT to become ACTIVE. After this, the framework ramps up to it's initial start level and all the autoinstall bundles are started for FRAMEWORK_ACTIVE to become ACTIVE (which you also see @ INFO level). Only then the service status report is printed, which by then is obviously not in sync with the actual service states.

Is that possible?
                
> Controller incorrectly reports missing service dependencies
> -----------------------------------------------------------
>
>                 Key: AS7-4603
>                 URL: https://issues.jboss.org/browse/AS7-4603
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: OSGi, Server
>            Reporter: Thomas Diesler
>            Assignee: Brian Stansberry
>             Fix For: 7.1.2.Final (EAP)
>
>
> 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.
> {code}
> 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] 
> {code}
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira