[jboss-jira] [JBoss JIRA] (AS7-5445) deploy --name=(name with no extension) failed sometimes

[Cheng Fang (JIRA)]

Cheng Fang created AS7-5445:
-------------------------------

             Summary: deploy --name=(name with no extension) failed sometimes
                 Key: AS7-5445
                 URL: https://issues.jboss.org/browse/AS7-5445
             Project: Application Server 7
          Issue Type: Bug
          Components: Domain Management
    Affects Versions: 7.1.2.Final (EAP)
            Reporter: Cheng Fang
            Assignee: Brian Stansberry


When deploying an app with --name option to specify a custom name, does the custom name have to include file extension to indicate its archive type?  For example, is --name="nnn" valid, or does it have to be --name="nnn.war"?  It seem requiring an archive type on a name is too restrictive.

This is what I've observed:

deploy --name="nnn" /tmp/hello.war deployed successfully, but there is no registration of web app context, so no way to run the webapp.  Looks like the server haven't detected that it is a webapp from the name "nnn", and instead deployed it as a pojo module.  With --name="nnn.war", everything works fine.

deploy --name="nnn" /tmp/test-ejb.jar deployed successfully, and all the ejb's are registered.

deploy --name="nnn" /tmp/test.ear deployed successfully, but ejb's inside the test.ear are not registered.

deploy --name="nnn" /tmp/ejb-in-war.war failed, which could be the same cause as in the pure webapp deploy:
{noformat}
21:47:14,391 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-10) MSC00001: Failed to start service jboss.deployment.unit.nnn.POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit.nnn.POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of deployment "nnn"
	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_33]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_33]
	at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_33]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.lang.ClassNotFoundException: test.TestBean from [Module "deployment.nnn:main" from Service Module Loader]
	at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.getEjbClass(BusinessViewAnnotationProcessor.java:216)
	at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.deploy(BusinessViewAnnotationProcessor.java:86)
	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
	... 5 more
Caused by: java.lang.ClassNotFoundException: test.TestBean from [Module "deployment.nnn:main" from Service Module Loader]
	at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.3.GA]
	at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.3.GA]
	at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.3.GA]
	at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.3.GA]
	at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) [jboss-modules.jar:1.1.3.GA]
	at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.getEjbClass(BusinessViewAnnotationProcessor.java:214)
	... 7 more
{noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira