Deployment fails when specifying --name=xyz (JBoss CLI deploy)
tholewebgods Feb 13, 2013 6:52 AMHello.
I'm trying to deploy my Application using the JBoss CLI deploy command with --name switch.
Without specifying --name, the deployment works perfectly. With specifying any name (only [a-z]) it will fail with vague error message.
11:17:51,754 INFO [org.jboss.as.server] (management-handler-thread - 12) JBAS015870: Deploy of deployment "xyz" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.xxx.POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.xxx.POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of deployment \"xyz\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.lang.ClassNotFoundException: xxx.xxx.xxx.xxx.xxx.SomeOtherClass from [Module \"deployment.xxx:main\" from Service Module Loader]
Caused by: java.lang.ClassNotFoundException: xxx.xxx.xxx.xxx.xxx.SomeOtherClass from [Module \"deployment.xxx:main\" from Service Module Loader]"}}
11:17:51,759 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment xxx in 4ms
11:17:58,298 INFO [org.jboss.as.repository] (management-handler-thread - 9) JBAS014901: Content removed from location /home/jboss/EAP-6.0.1/jboss-eap-6.0/standalone/data/content/77/4b820957b57e3f758a38dd8ff7a9e6a4505187/content
11:18:20,942 INFO [org.jboss.as.repository] (management-handler-thread - 11) JBAS014900: Content added at location /home/jboss/EAP-6.0.1/jboss-eap-6.0/standalone/data/content/77/4b820957b57e3f758a38dd8ff7a9e6a4505187/content
When compared to deployment without --name, where JBoss tries to read the persistence.xml successfully it seems to stop there, when using --name.
This works well, when omitting --name:
11:49:39,377 INFO [org.jboss.as.jpa] (MSC service thread 1-3) JBAS011401: Read persistence.xml for xyzPU
11:49:39,560 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment xxx-0.5-SNAPSHOT.war
11:49:39,571 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named SomeClass in deployment unit deployment "xxx-0.5-SNAPSHOT.war" are as follows:
...
11:49:39,571 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named SomeOtherClass in deployment unit deployment "xxx-0.5-SNAPSHOT.war" are as follows:
...
As we can see, the Read persistence.xml is missing in the first log, so we can assume it doesn't get this far. So does it have to do with the persistence.xml?
Environment:
- x86-64
- RedHat 6
- EAP 6.0.1 / JBoss 7.1.3 (evaluation package)
- Oracle 1.7 JDK
- standalone-full profile
Please help me.