11 Replies Latest reply on Jun 25, 2009 3:24 PM by jaikiran pai

    DeploymentException bootstrap/logging.xml & bootstrap/vfs.xm

    Andrew Tillinghast Newbie

      Having a problem that on jboss start messaging isn't creating tables and I'm getting no errors. Checking my boot.log I found an error, while I don't think it has anything to do with the table create it might be why I'm not seeing an errors.

      In boot.log:

      19:22:10,497 DEBUG [AbstractDeploymentContext] Added component LogBridgeHandler to file:/opt/jboss/server/default/conf/bootstrap/logging.xml
      19:22:10,499 DEBUG [ProfileServiceBootstrap] Failed to build ManagedDeployment for: AbstractKernelDeployment@5d18a770{name=file:/opt/jboss/server/default/conf/bootstrap/logging.xml installed=true beanFactories=[AbstractBeanMetaData@7d98d9cf{name=LogBridgeHandler bean=org.jboss.logbridge.LogBridgeHandler properties= constructor=null autowireCandidate=true}]}
      org.jboss.deployers.spi.DeploymentException: Error deploying: file:/opt/jboss/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:433)
       at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:250)
       at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
       at org.jboss.Main.boot(Main.java:221)
       at org.jboss.Main$1.run(Main.java:556)
       at java.lang.Thread.run(Thread.java:619)
      Caused by: java.lang.IllegalStateException: ClassLoader has not been set
       at org.jboss.deployers.structure.spi.helpers.AbstractDeploymentUnit.getClassLoader(AbstractDeploymentUnit.java:154)
       at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.addBeanComponent(BeanMetaDataFactoryVisitor.java:60)
       at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:126)
       ... 6 more
      19:22:10,502 DEBUG [AbstractDeploymentContext] Added component VFSCache$realCache#1 to file:/opt/jboss/server/default/conf/bootstrap/vfs.xml
      19:22:10,502 DEBUG [ProfileServiceBootstrap] Failed to build ManagedDeployment for: AbstractKernelDeployment@6161c9d1{name=file:/opt/jboss/server/default/conf/bootstrap/vfs.xml installed=true beanFactories=[AbstractBeanMetaData@5b08ea49{name=VFSCache bean=null properties=[permanentRoots, realCache] constructor=AbstractConstructorMetaData@74c6eff5{parameters=[null] factoryClass=org.jboss.virtual.spi.cache.VFSCacheFactory factoryMethod=getInstance} autowireCandidate=true start=AbstractLifecycleMetaData@30b3f9b8{ whenRequired=ControllerState@264d8d50{Start} parameters= }}, AbstractBeanMetaData@2d7892d5{name=VfsNamesExceptionHandler bean=org.jboss.virtual.plugins.context.helpers.NamesExceptionHandler properties= constructor=AbstractConstructorMetaData@46eff545{parameters=[java.lang.String]} autowireCandidate=true}]}
      org.jboss.deployers.spi.DeploymentException: Error deploying: file:/opt/jboss/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:433)
       at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:250)
       at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
       at org.jboss.Main.boot(Main.java:221)
       at org.jboss.Main$1.run(Main.java:556)
       at java.lang.Thread.run(Thread.java:619)
      Caused by: java.lang.IllegalStateException: ClassLoader has not been set
       at org.jboss.deployers.structure.spi.helpers.AbstractDeploymentUnit.getClassLoader(AbstractDeploymentUnit.java:154)
       at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.addBeanComponent(BeanMetaDataFactoryVisitor.java:60)
       at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:126)
       ... 6 more
      19:22:10,503 DEBUG [AbstractDeploymentContext] Added component ClassLoaderSystem to file:/opt/jboss/server/default/conf/bootstrap/classloader.xml
      19:22:10,503 DEBUG [AbstractDeploymentContext] Added component ClassLoading to file:/opt/jboss/server/default/conf/bootstrap/classloader.xml
      19:22:10,503 DEBUG [AbstractDeploymentContext] Added component bootstrap-classloader:0.0.0 to file:/opt/jboss/server/default/conf/bootstrap/classloader.xml
      


      This is essentially an "out of the box" deploy, all I've done is set the jmx-console security settings and added a mssql-ds as my defaultDS. Removing the hsqldb-ds in the process of course.

      -Andrew

        • 1. Re: DeploymentException bootstrap/logging.xml & bootstrap/vf
          David Lloyd Master

          Out of what box? What version is this? Can you paste the console startup messages, which include your runtime config including the JDK in use, the operating system, etc.?

          • 2. Re: DeploymentException bootstrap/logging.xml & bootstrap/vf
            Andrew Tillinghast Newbie

            jboss-5.1.0.GA

            installed from jboss-5.1.0.GA-jdk6.zip

            =========================================================================
            
             JBoss Bootstrap Environment
            
             JBOSS_HOME: /opt/jboss
            
             JAVA: /usr/java/jdk1.6.0_14/bin/java
            
             JAVA_OPTS: -Dprogram.name=run.sh -server -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true
            
             CLASSPATH: /opt/jboss/bin/run.jar:/usr/java/jdk1.6.0_14/lib/tools.jar
            
            =========================================================================
            
            20:53:53,271 INFO [ServerImpl] Starting JBoss (Microcontainer)...
            20:53:53,272 INFO [ServerImpl] Release ID: JBoss [The Oracle] 5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)
            20:53:53,272 INFO [ServerImpl] Bootstrap URL: null
            20:53:53,273 INFO [ServerImpl] Home Dir: /opt/jboss
            20:53:53,273 INFO [ServerImpl] Home URL: file:/opt/jboss/
            20:53:53,273 INFO [ServerImpl] Library URL: file:/opt/jboss/lib/
            20:53:53,274 INFO [ServerImpl] Patch URL: null
            20:53:53,274 INFO [ServerImpl] Common Base URL: file:/opt/jboss/common/
            20:53:53,274 INFO [ServerImpl] Common Library URL: file:/opt/jboss/common/lib/
            20:53:53,274 INFO [ServerImpl] Server Name: default
            20:53:53,274 INFO [ServerImpl] Server Base Dir: /opt/jboss/server
            20:53:53,275 INFO [ServerImpl] Server Base URL: file:/opt/jboss/server/
            20:53:53,275 INFO [ServerImpl] Server Config URL: file:/opt/jboss/server/default/conf/
            20:53:53,275 INFO [ServerImpl] Server Home Dir: /opt/jboss/server/default
            20:53:53,275 INFO [ServerImpl] Server Home URL: file:/opt/jboss/server/default/
            20:53:53,275 INFO [ServerImpl] Server Data Dir: /opt/jboss/server/default/data
            20:53:53,275 INFO [ServerImpl] Server Library URL: file:/opt/jboss/server/default/lib/
            20:53:53,275 INFO [ServerImpl] Server Log Dir: /opt/jboss/server/default/log
            20:53:53,276 INFO [ServerImpl] Server Native Dir: /opt/jboss/server/default/tmp/native
            20:53:53,276 INFO [ServerImpl] Server Temp Dir: /opt/jboss/server/default/tmp
            20:53:53,276 INFO [ServerImpl] Server Temp Deploy Dir: /opt/jboss/server/default/tmp/deploy
            20:53:54,129 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/opt/jboss/server/default/conf/bootstrap.xml
            20:53:54,896 INFO [VFSCacheFactory] Initializing VFSCache [org.jboss.virtual.plugins.cache.CombinedVFSCache]
            20:53:54,899 INFO [VFSCacheFactory] Using VFSCache [CombinedVFSCache[real-cache: null]]
            20:53:55,262 INFO [CopyMechanism] VFS temp dir: /opt/jboss/server/default/tmp
            20:53:55,263 INFO [ZipEntryContext] VFS force nested jars copy-mode is enabled.
            20:53:56,985 INFO [ServerInfo] Java version: 1.6.0_14,Sun Microsystems Inc.
            20:53:56,985 INFO [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
            20:53:56,986 INFO [ServerInfo] Java VM: Java HotSpot(TM) 64-Bit Server VM 14.0-b16,Sun Microsystems Inc.
            20:53:56,986 INFO [ServerInfo] OS-System: Linux 2.6.18-128.1.14.el5,amd64
            20:53:56,987 INFO [ServerInfo] VM arguments: -Dprogram.name=run.sh -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -Djava.endorsed.dirs=/opt/jboss/lib/endorsed
            20:53:57,050 INFO [JMXKernel] Legacy JMX core initialized
            20:54:00,555 INFO [ProfileServiceBootstrap] Loading profile: ProfileKey@69c5a33b[domain=default, server=default, name=default]
            20:54:42,819 WARN [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
            20:54:43,039 WARN [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
            


            • 3. Re: DeploymentException bootstrap/logging.xml & bootstrap/vf
              jaikiran pai Master

              So is this a clean installation on which you are running into issues? Or have you done any changes to the downloaded AS?

              • 4. Re: DeploymentException bootstrap/logging.xml & bootstrap/vf
                Andrew Tillinghast Newbie

                Clean install, all I've done is set the jmx-console security settings and added a mssql-ds as my defaultDS. Removing the hsqldb-ds in the process of course

                • 5. Re: DeploymentException bootstrap/logging.xml & bootstrap/vf
                  Andrew Tillinghast Newbie

                  Also wanted to point out, it surprised me that these were debug messages, seems from the text of the message they should be errors.

                  • 6. Re: DeploymentException bootstrap/logging.xml & bootstrap/vf
                    jaikiran pai Master

                    So does the server start "successfully" (message on the console). I haven't looked for messages in server.log when the server is booting, maybe i too will see the same messages, *if i turn DEBUG logging on*?



                    Clean install, all I've done is set the jmx-console security settings and added a mssql-ds as my defaultDS. Removing the hsqldb-ds in the process of course


                    Not even changed jboss-log4j.xml? By default the logging level is set to INFO so i would not expect those DEBUG messages.

                    • 7. Re: DeploymentException bootstrap/logging.xml & bootstrap/vf
                      Andrew Tillinghast Newbie

                      Server starts "successfully" and there are no messages in the server.log. These messages are coming up in the boot.log. I didn't change the log threshold so it seems that whatever logs to boot.log is defaulting at debug.

                      When the system starts up everything seems to be functioning, I can access the jmx-console with the user/password I set in the properties file.

                      I was poking around in the log files however because I'm not seeing the JBoss tables be created/initialized in the MS SQL database. There aren't any errors or warnings pertaining to the DB in my server log so I checked the boot.log. That's when I found these messages. I don't think these messages have anything to do with the tables not being created but I was thinking that a fail on /bootstrap/logging.xml might actually be preventing my actual Database issues from being logged to server.log


                      • 8. Re: DeploymentException bootstrap/logging.xml & bootstrap/vf
                        jaikiran pai Master

                         

                        "giddion" wrote:
                        Server starts "successfully" and there are no messages in the server.log. These messages are coming up in the boot.log.


                        Okay, so it's the boot.log. I see those log messages too:

                        18:04:12,234 DEBUG [ProfileServiceBootstrap] Failed to build ManagedDeployment for: AbstractKernelDeployment@1afe17b{name=file:/home/jaikiran/MyStuff/jboss-5.1.0.GA/server/default/conf/bootstrap/logging.xml installed=true beanFactories=[AbstractBeanMetaData@1fc6dc6{name=LogBridgeHandler bean=org.jboss.logbridge.LogBridgeHandler properties= constructor=null autowireCandidate=true}]}
                        org.jboss.deployers.spi.DeploymentException: Error deploying: file:/home/jaikiran/MyStuff/jboss-5.1.0.GA/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:433)
                         at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:250)
                         at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
                         at org.jboss.Main.boot(Main.java:221)
                         at org.jboss.Main$1.run(Main.java:556)
                         at java.lang.Thread.run(Thread.java:595)
                        Caused by: java.lang.IllegalStateException: ClassLoader has not been set
                         at org.jboss.deployers.structure.spi.helpers.AbstractDeploymentUnit.getClassLoader(AbstractDeploymentUnit.java:154)
                         at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.addBeanComponent(BeanMetaDataFactoryVisitor.java:60)
                         at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:126)
                         ... 6 more
                        


                        So i don't think they will cause any harm (as they have always been there). Having said that, i guess we need to see why those errors are being reported.


                        because I'm not seeing the JBoss tables be created/initialized in the MS SQL database.


                        Are you talking about JMS tables or are those your application specific tables? If it's the JMS tables then i remember there was property in a xml file which had to be set to create those tables (something along the lines of create-tables-on-startup)



                        • 9. Re: DeploymentException bootstrap/logging.xml & bootstrap/vf
                          Andrew Tillinghast Newbie

                          Yes I'm talking about the JMS tables, I'll have to look for that xml setting but in the jmx-console it indicates I have create on startup set.

                          • 10. Re: DeploymentException bootstrap/logging.xml & bootstrap/vf
                            Ales Justin Master

                             

                            "jaikiran" wrote:

                            So i don't think they will cause any harm (as they have always been there). Having said that, i guess we need to see why those errors are being reported.

                            I think this is the issue / cause:
                            - http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4231545#4231545

                            • 11. Re: DeploymentException bootstrap/logging.xml & bootstrap/vf
                              jaikiran pai Master

                               

                              "giddion" wrote:
                              Yes I'm talking about the JMS tables, I'll have to look for that xml setting but in the jmx-console it indicates I have create on startup set.


                              FYI for others reading this. This has been resolved here http://www.jboss.org/index.html?module=bb&op=viewtopic&t=157621