[jboss-as7-dev] NPEs when EE subsystem is disabled
Carlo de Wolf
cdewolf at redhat.com
Wed Mar 21 07:40:15 EDT 2012
This is mostly just mierenneuken.
If the EE subsystem is disabled you get interesting NPEs from other subsystems (for obvious reasons).
09:27:12,934 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deployment.unit."node-info.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."node-info.war".PARSE: Failed to process phase PARSE of deployment "node-info.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.0.Final.jar:7.1.0.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_b147-icedtea]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_b147-icedtea]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_b147-icedtea]
Caused by: java.lang.NullPointerException
at org.jboss.as.ejb3.deployment.processors.EjbContextJndiBindingProcessor.deploy(EjbContextJndiBindingProcessor.java:68)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.0.Final.jar:7.1.0.Final]
... 5 more
Do we want to have a more friendly message when dependent subsystems are not available?
Carlo
More information about the jboss-as7-dev
mailing list