[jboss-user] [JBoss Web Services] New message: "Issues with JBoss 5.1.0 GA and JBossWS CXF 3.2.2 GA"

Michael Maretzke do-not-reply at jboss.com
Mon Feb 22 11:38:20 EST 2010


User development,

A new message was posted in the thread "Issues with JBoss 5.1.0 GA and JBossWS CXF 3.2.2 GA":

http://community.jboss.org/message/527657#527657

Author  : Michael Maretzke
Profile : http://community.jboss.org/people/maretzke

Message:
--------------------------------------------------------------
Hi guys,
 
we're using JBoss 5.1.0 GA and JBossWS CXF 3.2.2 GA on Ubuntu Linux 9.10 (x86 32 Bit). We've installed JBoss 5.1.0 in /opt/jboss-5.1.0 and followed the description on how to install JBossWS - which went all fine and without any (!) issues.
 
When running JBoss in the "default" configuration (e.g. "./run.sh -c default" or "./run.sh") JBoss starts up without any issues - indicating JBossWS installation went smooth and fine. I tested the system with a EAR file containing some WS invocations - everything went really nicely.
 
Starting the same installation with the "all" configuration (e.g. "./run.sh -c all") doesn't start as smoothly ... Right in the beginning of the server.log file it starts with:
 
2010-02-22 17:29:02,592 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (main) Error installing to Real: name=vfsfile:/opt/jboss-5.1.0/server/all/deployers/jbossws.deployer/ state=PreReal mode=Manual requiredState=Real
org.jboss.deployers.spi.DeploymentException: Error deploying: vfsfile:/opt/jboss-5.1.0/server/all/deployers/jbossws.deployer/
    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.deployers.spi.deployer.helpers.AbstractRealDeployerWithInput.deploy(AbstractRealDeployerWithInput.java:125)
    at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployerWithInput.internalDeploy(AbstractRealDeployerWithInput.java:102)
    at org.jboss.deployers.spi.deployer.helpers.AbstractComponentDeployer.internalDeploy(AbstractComponentDeployer.java:78)
    at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
    at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
    at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
    at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
    at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
    at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
    at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
    at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
    at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
    at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
    at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
    at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
    at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
    at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
    at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
    at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)
    at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)
    at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361)
    at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
    at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
    at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
    at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
    at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
    at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
    at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
    at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306)
    at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271)
    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.IllegalArgumentException: Exception loading class for ScopeKey addition.
    at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.addBeanComponent(BeanMetaDataFactoryVisitor.java:67)
    at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:126)
    ... 34 more
Caused by: java.lang.ClassNotFoundException: org.jboss.wsf.spi.util.KernelLocator from BaseClassLoader at 477b4e{VFSClassLoaderPolicy at f0691c{name=vfsfile:/opt/jboss-5.1.0/server/all/deployers/jbossws.deployer/ domain=ClassLoaderDomain at ed32c4{name=DefaultDomain parentPolicy=BEFORE parent=org.jboss.bootstrap.NoAnnotationURLClassLoader at 118f375}
 
Because of this error listed above, JBoss can't deploy the mentioned EAR file (which worked nicely in "default").
 
The root cause "java.lang.ClassNotFoundException: org.jboss.wsf.spi.util.KernelLocator" catched my attention and it turned out that no JAR file on my system did contain the searched-for class. Interestingly, JBossWS 3.2.0 contains the missing class in "jbossws-spi.jar". Putting this one single class from jbossws-spi.jar (version 3.2.0) to jbossws-spi.jar (version 3.2.2) lead to another missing class: org.jboss.wsf.spi.metadata.j2ee.EJBArchiveMetaData$PublishLocationAdapter.
 
There I stopped and searched the internet with no usable result.
 
Do you guys have the same issue? Any suggestion on a resolution?
 
Any feedback appreciated!!
 
With best regards,
Michael.

--------------------------------------------------------------

To reply to this message visit the message page: http://community.jboss.org/message/527657#527657




More information about the jboss-user mailing list