[jboss-jira] [JBoss JIRA] Commented: (AS7-1143) Should pre-populated modules a high start level be loaded in lower start levels?
Thomas Diesler (JIRA)
jira-events at lists.jboss.org
Wed Jul 27 07:55:24 EDT 2011
[ https://issues.jboss.org/browse/AS7-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616993#comment-12616993 ]
Thomas Diesler commented on AS7-1143:
-------------------------------------
Theoretically possible. However, it is also possible that bundle at sl=x wires to a bundle at sl=x+n. The log shows that it takes <460ms to install the complete set of bundles.
> Should pre-populated modules a high start level be loaded in lower start levels?
> --------------------------------------------------------------------------------
>
> Key: AS7-1143
> URL: https://issues.jboss.org/browse/AS7-1143
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi
> Affects Versions: 7.0.0.CR1
> Reporter: David Bosschaert
> Priority: Optional
>
> A number of modules are specified to be pre-loaded in the OSGi framework in the <modules> section of the osgi subsystem configuration.
> {code}<modules>
> <module identifier="javaee.api"/>
> <module identifier="org.jboss.logging"/>
> <module identifier="org.apache.aries.util"/>
> <module identifier="org.jboss.osgi.webconsole"/>
> <module identifier="org.osgi.compendium"/>
> <module identifier="org.apache.felix.log" startlevel="1"/>
> <module identifier="org.jboss.osgi.logging" startlevel="1"/>
> <module identifier="org.apache.felix.configadmin" startlevel="1"/>
> <module identifier="org.jboss.as.osgi.configadmin" startlevel="1"/>
> <module identifier="org.apache.aries.jmx" startlevel="2"/>
> <module identifier="org.apache.felix.eventadmin" startlevel="2"/>
> <module identifier="org.apache.felix.metatype" startlevel="2"/>
> <module identifier="org.apache.felix.webconsole" startlevel="2"/>
> <module identifier="org.jboss.osgi.jmx" startlevel="2"/>
> <module identifier="org.jboss.osgi.http" startlevel="2"/>
> <module identifier="org.jboss.osgi.blueprint" startlevel="3"/>
> <module identifier="org.jboss.osgi.webapp" startlevel="3"/>
> <module identifier="org.jboss.osgi.xerces" startlevel="3"/>
> </modules>{code}
> Currently all modules are loaded, regardless of start level and only those that have a start level <= the current one are actually started. I wonder whether this is desirable. When a module has a startlevel specified, it clearly needs to be started and is likely not useful when not started. It would therefore make sense to me to not pre-load modules with a higher start level, but only load these once their start level is being reached. This would improve subsystem start times too...
> I.e. even when start level 1 is specified, the following output appears when the framework is started:
> {code}13:52:28,008 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-14) Install bundle: system.bundle:0.0.0
> 13:52:28,119 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-6) Install bundle: javaee.api:0.0.0
> 13:52:28,119 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-10) Install bundle: org.jboss.logging:3.0.0
> 13:52:28,133 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-11) Install bundle: jboss-as-osgi-configadmin:7.0.0.CR1
> 13:52:28,137 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-2) Install bundle: jbosgi-webconsole:1.0.6
> 13:52:28,140 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-12) Install bundle: jboss-osgi-logging:1.0.0
> 13:52:28,176 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-7) Install bundle: jboss-osgi-jmx:1.0.10
> 13:52:28,204 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-5) Install bundle: org.apache.felix.metatype:1.0.4
> 13:52:28,219 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-1) Install bundle: org.apache.felix.configadmin:1.2.8
> 13:52:28,228 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-6) Install bundle: org.apache.aries.util:0.3.0
> 13:52:28,229 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-14) Install bundle: org.apache.aries.jmx:0.3.0
> 13:52:28,237 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-11) Install bundle: org.apache.felix.log:1.0.0
> 13:52:28,240 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-16) Install bundle: jbosgi-blueprint:1.0.2
> 13:52:28,313 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: jbosgi-webapp:1.0.2
> 13:52:28,325 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-8) Install bundle: org.apache.felix.eventadmin:1.2.6
> 13:52:28,333 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-9) Install bundle: jboss-osgi-xerces:2.9.1.SP7
> 13:52:28,368 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-13) Install bundle: org.apache.felix.webconsole:3.1.6.SP1
> 13:52:28,394 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-15) Install bundle: jboss-osgi-http:1.0.3
> 13:52:28,460 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-4) Install bundle: osgi.cmpn:4.2.0.200908310645
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list