WAR file works on tomcat but will not install on JBoss EAP 5.1?
WAR file works on tomcat but will not install on JBoss EAP 5.1?
WAR file works on tomcat but will not install on JBoss EAP 5.1?.
I am using the admin console to upload my war file and I am getting the following error..
java.lang.RuntimeException: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** DEPLOYMENTS IN ERROR: Name -> Error
vfsfile:/var/lib/jbossas/server/default/deploy/MemberInquiry.war/ -> org.jboss.deployers.spi.DeploymentException: URL file:/var/lib/jbossas/server/default/deploy/MemberInquiry.war/ deployment failed
DEPLOYMENTS IN ERROR:
Deployment "vfsfile:/var/lib/jbossas/server/default/deploy/MemberInquiry.war/" is in error due to the following reason(s): org.jboss.deployers.spi.DeploymentException: URL file:/var/lib/jbossas/server/default/deploy/MemberInquiry.war/ deployment failed
at org.jboss.profileservice.management.client.upload.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:312)
at org.jboss.profileservice.management.client.upload.StreamingDeploymentTarget.start(StreamingDeploymentTarget.java:189)
at org.jboss.profileservice.management.client.upload.DeploymentProgressImpl.start(DeploymentProgressImpl.java:232)
at org.jboss.profileservice.management.client.upload.DeploymentProgressImpl.run(DeploymentProgressImpl.java:89)
at org.rhq.plugins.jbossas5.util.DeploymentUtils.run(DeploymentUtils.java:136)
at org.rhq.plugins.jbossas5.AbstractManagedDeploymentComponent.invokeOperation(AbstractManagedDeploymentComponent.java:160)
at sun.reflect.GeneratedMethodAccessor1598.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:525)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
Caused by: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** DEPLOYMENTS IN ERROR: Name -> Error
vfsfile:/var/lib/jbossas/server/default/deploy/MemberInquiry.war/ -> org.jboss.deployers.spi.DeploymentException: URL file:/var/lib/jbossas/server/default/deploy/MemberInquiry.war/ deployment failed
DEPLOYMENTS IN ERROR:
Deployment "vfsfile:/var/lib/jbossas/server/default/deploy/MemberInquiry.war/" is in error due to the following reason(s): org.jboss.deployers.spi.DeploymentException: URL file:/var/lib/jbossas/server/default/deploy/MemberInquiry.war/ deployment failed
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1008)
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:954)
at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:870)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128)
at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.start(AbstractDeployHandler.java:326)
at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.invoke(AbstractDeployHandler.java:238)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:967)
at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
at org.jboss.remoting.Client.invoke(Client.java:2070)
at org.jboss.remoting.Client.invoke(Client.java:879)
at org.jboss.profileservice.management.client.upload.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:304)
... 14 more Responses
That error contains "Caused by: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS)", because it is just the summary of failed deployments at the end.
As it says, you need to look at the errors before that in the server.log file to find out why the particular deployment failed.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
