Problem Note 45882: DEBUG messages appear in the JBoss 5.1.x. Web application server's boot.log file
When you use the JBoss 5.1.x application server, the following DEBUG messages appear in the server's boot.log file. These messages are not indicative of a problem, so you can safely ignore the messages.
DEBUG [ProfileServiceBootstrap] Failed to build ManagedDeployment for: AbstractKernelDeployment@553abee1{name=file:/install/jboss/jboss-eap-5.1.1/jboss-as/server/SASServer2/conf/bootstrap/logging.xml installed=true beanFactories=[AbstractBeanMetaData@3c9d17e{name=LogBridgeHandler bean=org.jboss.logbridge.LogBridgeHandler properties= constructor=null autowireCandidate=true}]}
org.jboss.deployers.spi.DeploymentException: Error deploying: file:/install/jboss/jboss-eap-5.1.1/jboss-as/server/SASServer2/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: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: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)
. . .six more message lines. . .
DEBUG [ProfileServiceBootstrap] Failed to build ManagedDeployment for: AbstractKernelDeployment@153c765e{name=file:/install/jboss/jboss-eap-5.1.1/jboss-as/server/SASServer2/conf/bootstrap/vfs.xml installed=true beanFactories=[AbstractBeanMetaData@347f2036{name=VFSCache bean=null properties=[realCache, permanentRoots] constructor=AbstractConstructorMetaData@2a114025{parameters=[null] factoryClass=org.jboss.virtual.spi.cache.VFSCacheFactory factoryMethod=getInstance} autowireCandidate=true start=AbstractLifecycleMetaData@528a52b6{ whenRequired=ControllerState@61bd427{Start} parameters= }}, AbstractBeanMetaData@d054f93{name=VfsNamesExceptionHandler bean=org.jboss.virtual.plugins.context.helpers.NamesExceptionHandler properties= constructor=AbstractConstructorMetaData@57ab4292{parameters=[java.lang.String]} autowireCandidate=true}]}
org.jboss.deployers.spi.DeploymentException: Error deploying: file:/install/jboss/jboss-eap-5.1.1/jboss-as/server/SASServer2/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: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: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)
. . .six more message lines. . .
Operating System and Release Information
SAS System | JBoss Application Server | Microsoft Windows XP Professional | 5.1.0 | | 9.3 TS1M0 | |
Microsoft Windows Server 2008 for x64 | 5.1.0 | | 9.3 TS1M0 | |
Microsoft Windows Server 2008 | 5.1.0 | | 9.3 TS1M0 | |
Microsoft Windows Server 2003 for x64 | 5.1.0 | | 9.3 TS1M0 | |
Microsoft Windows Server 2003 Standard Edition | 5.1.0 | | 9.3 TS1M0 | |
Microsoft Windows Server 2003 Enterprise Edition | 5.1.0 | | 9.3 TS1M0 | |
Microsoft Windows Server 2003 Datacenter Edition | 5.1.0 | | 9.3 TS1M0 | |
Microsoft® Windows® for x64 | 5.1.0 | | 9.3 TS1M0 | |
Windows 7 Enterprise 32 bit | 5.1.0 | | 9.3 TS1M0 | |
Windows 7 Enterprise x64 | 5.1.0 | | 9.3 TS1M0 | |
Windows 7 Home Premium 32 bit | 5.1.0 | | 9.3 TS1M0 | |
Windows 7 Home Premium x64 | 5.1.0 | | 9.3 TS1M0 | |
Windows 7 Professional 32 bit | 5.1.0 | | 9.3 TS1M0 | |
Windows 7 Professional x64 | 5.1.0 | | 9.3 TS1M0 | |
Windows 7 Ultimate 32 bit | 5.1.0 | | 9.3 TS1M0 | |
Windows 7 Ultimate x64 | 5.1.0 | | 9.3 TS1M0 | |
Windows Vista | 5.1.0 | | 9.3 TS1M0 | |
Windows Vista for x64 | 5.1.0 | | 9.3 TS1M0 | |
64-bit Enabled AIX | 5.1.0 | | 9.3 TS1M0 | |
64-bit Enabled Solaris | 5.1.0 | | 9.3 TS1M0 | |
HP-UX IPF | 5.1.0 | | 9.3 TS1M0 | |
Linux for x64 | 5.1.0 | | 9.3 TS1M0 | |
Solaris for x64 | 5.1.0 | | 9.3 TS1M0 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | medium |
Date Modified: | 2012-08-08 10:48:16 |
Date Created: | 2012-03-02 09:28:30 |