]
Jason Greene reopened JBAS-8039:
--------------------------------
Due to feedback from the community, I have split the AS7 and AS6 projects and reopened all
unscheduled AS6 issues that are a year or less old. This will make it easier community
members to find and work on them.
Future releases beyond 6.1 can be done provided a community member steps up to coordinate
them.
Failed to start a JAXWS war deployment
---------------------------------------
Key: JBAS-8039
URL:
https://issues.jboss.org/browse/JBAS-8039
Project: Legacy JBoss Application Server 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: JBossAS-5.1.0.GA, 6.0.0.M2
Environment: RHEL
Reporter: jay ZHAO
Fix For: No Release
We have a JAXWS war file which has been successfully deployed to GlassFish, WebSphere and
WebLogic, but cannot be deployed to JBoss AS 5.1 and 6.0.0.M2. Here are the 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/ ->
: 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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: