Uploaded image for project: 'Application Server 7'
  1. Application Server 7
  2. AS7-5029

Invalid wait for ConfigurationAdmin service

XMLWordPrintable

      The effect is that server startup may hang for 10sec.

      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

      Note the delay between 09:15:01 and 09:15:11

      This is very likely caused by this code in DomainModelPersistenceManager

              ConfigurationAdmin osgiConfigAdminService = (ConfigurationAdmin) osgiConfigAdminServiceTracker.waitForService(10000);

              dhildenb@redhat.com David Hildenbrand
              tdiesler@redhat.com Thomas Diesler
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: