Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-11077

During EAP startup this type of errors are shown in boot.log: java.lang.IllegalStateException: ClassLoader has not been set

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Out of Date
    • Affects Version/s: EAP_EWP 5.3.0.ER3
    • Fix Version/s: EAP_EWP 5.3.1.GA
    • Component/s: Build
    • Labels:
      None
    • Docs QE Status:
      NEW

      Description

      In logs appears exception messages with stacktrace on clean startup (connected to some config deployments):

      13:06:01,180 DEBUG [ProfileServiceBootstrap] Failed to build ManagedDeployment for: AbstractKernelDeployment@379c4f3b{name=file:/home/rhatlapa/projects/redhat_projects/eap/repo/5.3/jboss-eap-5.3/jboss-as/server/default/conf/bootstrap/vfs.x
      org.jboss.deployers.spi.DeploymentException: Error deploying: file:/home/rhatlapa/projects/redhat_projects/eap/repo/5.3/jboss-eap-5.3/jboss-as/server/default/conf/bootstrap/vfs.xml
        at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
        at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:136)
        at org.jboss.system.server.profileservice.ProfileServiceBootstrap.initBootstrapMDs(ProfileServiceBootstrap.java:426)
        at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:242)
        at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
        at org.jboss.Main.boot(Main.java:229)
        at org.jboss.Main$1.call(Main.java:561)
        at org.jboss.Main$1.call(Main.java:557)
        at java.util.concurrent.FutureTask.run(FutureTask.java:262)
        at java.lang.Thread.run(Thread.java:744)
      Caused by: java.lang.IllegalStateException: ClassLoader has not been set
        at org.jboss.deployers.structure.spi.helpers.AbstractDeploymentUnit.getClassLoader(AbstractDeploymentUnit.java:159)
        at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.addBeanComponent(BeanMetaDataFactoryVisitor.java:60)
        at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:126)
        ... 8 more
      13:06:01,182 DEBUG [AbstractDeploymentContext] Added component LogBridgeHandler to file:/home/rhatlapa/projects/redhat_projects/eap/repo/5.3/jboss-eap-5.3/jboss-as/server/default/conf/bootstrap/logging.xml
      13:06:01,182 DEBUG [ProfileServiceBootstrap] Failed to build ManagedDeployment for: AbstractKernelDeployment@4f3a2bf2{name=file:/home/rhatlapa/projects/redhat_projects/eap/repo/5.3/jboss-eap-5.3/jboss-as/server/default/conf/bootstrap/loggi
      org.jboss.deployers.spi.DeploymentException: Error deploying: file:/home/rhatlapa/projects/redhat_projects/eap/repo/5.3/jboss-eap-5.3/jboss-as/server/default/conf/bootstrap/logging.xml
        at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
        at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:136)
        at org.jboss.system.server.profileservice.ProfileServiceBootstrap.initBootstrapMDs(ProfileServiceBootstrap.java:426)
        at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:242)
        at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
        at org.jboss.Main.boot(Main.java:229)
        at org.jboss.Main$1.call(Main.java:561)
        at org.jboss.Main$1.call(Main.java:557)
        at java.util.concurrent.FutureTask.run(FutureTask.java:262)
        at java.lang.Thread.run(Thread.java:744)
      Caused by: java.lang.IllegalStateException: ClassLoader has not been set
        at org.jboss.deployers.structure.spi.helpers.AbstractDeploymentUnit.getClassLoader(AbstractDeploymentUnit.java:159)
        at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.addBeanComponent(BeanMetaDataFactoryVisitor.java:60)
        at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:126)
        ... 8 more
      

      The startup should be clean. If it is expected Exception it shouldn't at least print stacktrace to logs.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                jboss-set JBoss SET
                Reporter:
                rhatlapa Radim Hatlapatka
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: