[jboss-jira] [JBoss JIRA] Commented: (JBAS-8033) Can not deploy JAXWS war file to Jboss 5.1 and 6.0.0.M2

jay ZHAO (JIRA) jira-events at lists.jboss.org
Wed May 19 11:20:06 EDT 2010 

    [ https://jira.jboss.org/browse/JBAS-8033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12531511#action_12531511 ] 

jay ZHAO commented on JBAS-8033:
--------------------------------

The war file we have contains some old j2ee and derby jar files, after removed them, we passed the old errors (we are still not sure why the same war can be deployed to other app servers, but not Jboss), but we got new errors:
2010-05-19 10:32:09,746 ERROR [org.rhq.plugins.jbossas5.deploy.LocalDeployer] (ResourceContainer.invoker.nonDaemon-5) Error deploying application for request [CreateResourceReport: ResourceType=[ResourceType[id=0, category=Service, name=Web Application (WAR), plugin=JBossAS5]], ResourceKey=[null]].: java.lang.Exception: Failed to start deployment [vfszip:/opt/jboss-6.0.0.20100216-M2/server/default/deploy/JAXWSDiscoveryService.war/] during deployment of 'JAXWSDiscoveryService.war' - cause: java.lang.RuntimeException:org.jboss.deployers.spi.DeploymentException: Deployment context not found: vfszip:/opt/jboss-6.0.0.20100216-M2/server/default/deploy/JAXWSDiscoveryService.war/ -> org.jboss.deployers.spi.DeploymentException:Deployment context not found: vfszip:/opt/jboss-6.0.0.20100216-M2/server/default/deploy/JAXWSDiscoveryService.war/
	at org.rhq.plugins.jbossas5.util.DeploymentUtils.deployArchive(DeploymentUtils.java:146)
	at org.rhq.plugins.jbossas5.deploy.AbstractDeployer.deploy(AbstractDeployer.java:110)
	at org.rhq.plugins.jbossas5.ApplicationServerComponent.createContentBasedResource(ApplicationServerComponent.java:473)
	at org.rhq.plugins.jbossas5.ApplicationServerComponent.createResource(ApplicationServerComponent.java:295)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:525)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:619)

We are not sure what deployment context means here and what Jboss is expected.  We don’t have jboss-web.xml file in war file.  We could not find a clear instruction on whether we need jboss-web.xml or not.  Some of our war files without jboss-web.xml still can be deployed successfully, but some not. We also could not find a good instruction on how to create one if we need.  
Thanks for your quick response!
jay

> Can not deploy JAXWS war file to Jboss 5.1 and 6.0.0.M2
> -------------------------------------------------------
>
>                 Key: JBAS-8033
>                 URL: https://jira.jboss.org/browse/JBAS-8033
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Deployers
>    Affects Versions: JBossAS-5.1.0.GA, 6.0.0.M2
>         Environment: RHEL 2.6.18-194.el5
>            Reporter: jay ZHAO
>            Assignee: Remy Maucherat
>
> We have a JAXWS war file which has been successfully deployed to GlassFish and WebLogic, but cannot be deployed to JBoss AS 5.1 and 6.0.0.M2. On AS 5.1 there is no detailed log info, here is the error log on 5.1:
> DEPLOYMENTS IN ERROR:
>   Deployment "vfszip:/opt/jboss-5.1.0.GA/configurations/discovery/deploy/JAXWSDiscoveryService.war/" is in error due to the following reason(s): org.jboss.deployers.spi.DeploymentException: URL file:/opt/jboss-5.1.0.GA/server/default/tmp/4sge1w-qbnvnk-g9bavwnj-1-g9d3hmos-4t8/JAXWSDiscoveryService.war/ deployment failed
> 	at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993)
> 	at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:939)
> 	at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:873)
> 	at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128)
> 	at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.start(AbstractDeployHandler.java:265)
> 	at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.invoke(AbstractDeployHandler.java:177)
> 	at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
> 	at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
> 	at org.jboss.remoting.Client.invoke(Client.java:1724)
> 	at org.jboss.remoting.Client.invoke(Client.java:629)
> 	at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:305)
> 	... 16 more
> 2010-05-18 15:06:31,508 INFO  [org.jboss.profileservice.management.upload.remoting.DeployHandler] (ResourceContainer.invoker.nonDaemon-15) Remove, [vfszip:/opt/jboss-5.1.0.GA/configurations/discovery/deploy/JAXWSDiscoveryService.war/]
> 2010-05-18 15:06:31,523 WARN  [org.rhq.core.pc.inventory.CreateResourceRunner] (ResourceFactory.executor-1) Throwable was found in creation report for request [1]: java.lang.RuntimeException: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> *** DEPLOYMENTS IN ERROR: Name -> Error
> vfszip:/opt/jboss-5.1.0.GA/configurations/discovery/deploy/JAXWSDiscoveryService.war/ -> org.jboss.deployers.spi.DeploymentException: URL file:/opt/jboss-5.1.0.GA/server/default/tmp/4sge1w-qbnvnk-g9bavwnj-1-g9d3hmos-4t8/JAXWSDiscoveryService.war/ deployment failed 
> The errors we got when we deployed the same war file to 6.0.0.M2 are:
> Caused by: java.lang.LinkageError: loader constraint violation in interface itable initialization: when resolving method "org.apache.derby.jdbc.EmbedXAConnection.getXAResource()Ljavax/transaction/xa/XAResource;" the class loader (instance of org/jboss/classloader/spi/base/BaseClassLoader) of the current class, org/apache/derby/jdbc/EmbedXAConnection, and the class loader (instance of <bootloader>) for interface javax/sql/XAConnection have different Class objects for the type javax/transaction/xa/XAResource used in the signature
> 	at java.lang.Class.getDeclaredMethods0(Native Method)
> 	at java.lang.Class.privateGetDeclaredMethods(Class.java:2427)
> 	at java.lang.Class.getDeclaredMethods(Class.java:1791)
> 	at org.jboss.deployment.AnnotatedClassFilter.hasAnnotations(AnnotatedClassFilter.java:194)
> 	at org.jboss.deployment.AnnotatedClassFilter.accepts(AnnotatedClassFilter.java:122)
> 	at org.jboss.deployment.AnnotatedClassFilter.visit(AnnotatedClassFilter.java:102)
> 	at org.jboss.virtual.plugins.vfs.helpers.WrappingVirtualFileHandlerVisitor.visit(WrappingVirtualFileHandlerVisitor.java:62)
> 	at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:362)
> 	at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:374)
> 	at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:374)
> 	at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:374)
> 	at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:374)
> 	at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:307)
> 	at org.jboss.virtual.VFS.visit(VFS.java:438)
> 	at org.jboss.virtual.VirtualFile.visit(VirtualFile.java:448)
> 	at org.jboss.web.deployers.WarAnnotationMetaDataDeployer.getClasses(WarAnnotationMetaDataDeployer.java:180)
> 	at org.jboss.web.deployers.WarAnnotationMetaDataDeployer.processMetaData(WarAnnotationMetaDataDeployer.java:153)
> 	at org.jboss.web.deployers.WarAnnotationMetaDataDeployer.deploy(WarAnnotationMetaDataDeployer.java:127)
> 	at org.jboss.web.deployers.WarAnnotationMetaDataDeployer.deploy(WarAnnotationMetaDataDeployer.java:80)
> 	at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179)
> 	... 39 more
> 2010-05-18 10:45:15,790 INFO  [org.jboss.profileservice.management.upload.remoting.DeployHandler] (ResourceContainer.invoker.nonDaemon-2) Failed to complete command: [start] for deployment: names=[vfszip:/opt/jboss-6.0.0.20100216-M2/server/default/deploy/JAXWSDiscoveryService.war/]: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS)
> We have not seen the same problem in other major AS platforms. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

More information about the jboss-jira mailing list