[jboss-jira] [JBoss JIRA] (AS7-5029) Invalid wait for ConfigurationAdmin service

Wed Jun 20 03:32:12 EDT 2012

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

Thomas Diesler edited comment on AS7-5029 at 6/20/12 3:31 AM:
--------------------------------------------------------------

The same thread first start the AS integration bundle and then the felix config admin. 

{code}
09:15:11,065 INFO  [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011002: Bundle started: jboss-as-osgi-configadmin:7.2.0.Alpha1-SNAPSHOT
09:15:11,101 INFO  [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011002: Bundle started: org.apache.felix.configadmin:1.2.8
{code}

You cannot block that thread

      was (Author: thomas.diesler):
    The same thread first start the AS integration bundle and then the felix config admin. 

{code}
09:15:11,065 INFO  [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011002: Bundle started: jboss-as-osgi-configadmin:7.2.0.Alpha1-SNAPSHOT
09:15:11,101 INFO  [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011002: Bundle started: org.apache.felix.configadmin:1.2.8
{code}

> Invalid wait for ConfigurationAdmin service
> -------------------------------------------
>
>                 Key: AS7-5029
>                 URL: https://issues.jboss.org/browse/AS7-5029
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: ConfigAdmin, OSGi
>            Reporter: Thomas Diesler
>            Assignee: David Bosschaert
>             Fix For: 7.2.0.Alpha1
>
>
> The effect is that server startup may hang for 10sec.
> {code}
> 09:15:00,892 INFO  [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011011: Starting bundles for start level: 1
> 09:15:00,938 INFO  [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011002: Bundle started: jboss-osgi-logging:1.0.0
> 09:15:01,025 INFO  [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011002: Bundle started: org.apache.felix.log:1.0.0
> 09:15:01,222 INFO  [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on 127.0.0.1:9999
> 09:15:01,228 INFO  [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on 127.0.0.1:4447
> 09:15:01,258 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /home/tdiesler/git/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/deployments
> 09:15:11,065 INFO  [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011002: Bundle started: jboss-as-osgi-configadmin:7.2.0.Alpha1-SNAPSHOT
> 09:15:11,101 INFO  [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011002: Bundle started: org.apache.felix.configadmin:1.2.8
> 09:15:11,103 INFO  [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011000: OSGi Framework started
> {code}
> Note the delay between 09:15:01 and 09:15:11
> This is very likely caused by this code in DomainModelPersistenceManager
> {code}
>         ConfigurationAdmin osgiConfigAdminService = (ConfigurationAdmin) osgiConfigAdminServiceTracker.waitForService(10000);
> {code}

--
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