[jboss-jira] [JBoss JIRA] (AS7-4603) Controller incorrectly reports missing service dependencies
[
https://issues.jboss.org/browse/AS7-4603?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-4603:
---------------------------------------
Your comment in the last line of the description sounds correct to me. A management op
(and boot is just a huge management op) blocks until MSC reaches a stable point. Checking
for stability is done by means of a ServiceListener. If service
jbosgi.integration.PersistentBundlesHandler and service jbosgi.framework.INIT are missing
dependencies, but jbosgi.integration.AutoInstallHandler.COMPLETE has not been installed,
then the PersistentBundlesHandler and INIT services will be regarded as being in stable
states, the overall stability check will be complete and the "Service status
report" will be printed.
So, if the listener that checks for stability happens to get called before your listener
does, you get this situation.
A possibility is to install COMPLETE in Mode.NEVER in the normal way and then have the
listener switch it to Mode.ACTIVE. But TBH I doubt that will work; probably the same thing
would happen but with a slightly different error message.
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-redhat1
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