WAR deployments fail if EE subsystem removed -------------------------------------------- Key: AS7-2120 URL: https://issues.jboss.org/browse/AS7-2120 Project: Application Server 7 Issue Type: Bug Components: Web Affects Versions: 7.1.0.Alpha1, 7.0.2.Final Reporter: Tristan Tarrant Assignee: Stuart Douglas Priority: Minor If the org.jboss.as.ee extension is removed from the configuration, the deployment of WAR files doesn't work anymore. The following exception is thrown: {code} 14:49:53,938 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC00001: Failed to start service jboss.web.deployment.default-host./datagrid: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./datagrid: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1780) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_23] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_23] at java.lang.Thread.run(Thread.java:679) [:1.6.0_23] Caused by: java.lang.NullPointerException at java.util.ArrayDeque.addFirst(ArrayDeque.java:226) [:1.6.0_23] at java.util.ArrayDeque.push(ArrayDeque.java:493) [:1.6.0_23] at org.jboss.as.naming.util.ThreadLocalStack.push(ThreadLocalStack.java:43) at org.jboss.as.naming.context.NamespaceContextSelector.pushCurrentSelector(NamespaceContextSelector.java:48) at org.jboss.as.web.NamingValve.beginComponentStart(NamingValve.java:65) at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:62) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] ... 3 more {code} Looking at the code, it seems like the NamespaceContextSelector should be injected only if there is a moduleDescription. Unfortunately if it isn't (like in my case), it fails. If the moduleDescription should never be null, then a better exception should be thrown, otherwise the code shouldn't break. -- 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