-
1. Re: NPE in ComponentDescription$DefaultFirstConfigurator
jaikiran Aug 11, 2011 7:00 AM (in response to zlobniy)Can you please attach a application which reproduces this?
-
2. Re: NPE in ComponentDescription$DefaultFirstConfigurator
zlobniy Aug 12, 2011 1:19 AM (in response to jaikiran)Unfortunately I can not, it's a commercial project a large amount.
-
3. Re: NPE in ComponentDescription$DefaultFirstConfigurator
jaikiran Aug 12, 2011 1:25 AM (in response to zlobniy)Would you be able to narrow it down to what class in the application causes this issue? We first will have to be able to reproduce it before coming up with any relevant fix.
-
4. Re: NPE in ComponentDescription$DefaultFirstConfigurator
jean.baldessar Aug 19, 2011 1:27 PM (in response to jaikiran)I get this exception too:
14:23:37,104 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC00001: Failed to start service jboss.deployment.subunit."projedata.ear"."webprojedata.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."projedata.ear"."webprojedata.war".INSTALL: Failed to process phase INSTALL of subdeployment "webprojedata.war" of deployment "projedata.ear"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_23]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_23]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_23]
Caused by: java.lang.NullPointerException
at org.jboss.as.ee.component.ComponentDescription$DefaultFirstConfigurator.configure(ComponentDescription.java:532)
at org.jboss.as.ee.component.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:65)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 5 more
don't know what causes it
-
5. Re: NPE in ComponentDescription$DefaultFirstConfigurator
jean.baldessar Aug 19, 2011 1:44 PM (in response to zlobniy)Found the problem.
It's on the xml reading. My web.xml has this configuration:
<context-param>
<param-name>org.richfaces.LoadStyleStrategy</param-name>
<param-value>ALL</param-value> <!-- aumenta o tamanho da tela de login, mas diminui o tamanho de todas as requisições ajax -->
</context-param>
Removing the commant after the <param-value> tag, the application works.
Aleksandr, try to remove the web.xml comments.
-
6. Re: NPE in ComponentDescription$DefaultFirstConfigurator
shelleyb Aug 19, 2011 4:29 PM (in response to jean.baldessar)I just ran into this exact exception as well. It does appear to be caused by some configuration in the web.xml, but I've removed all comments from my deployment descriptors, so it's not the exact same cause. I'm working on narrowing down the root cause for the exception.
-
7. Re: NPE in ComponentDescription$DefaultFirstConfigurator
jean.baldessar Aug 19, 2011 4:47 PM (in response to shelleyb)Shelley Baker and Aleksandr Stepanov,
analyzing my web.xml again I get the real cause of the problem (at least my).
The problem was not the comment itself, but the special caracteres in it.
Removing the 'çõ' caracteres it worked. But I found one more thing that causes this exception: A filter declared with no mapping for it.
Removing the declaration of the filter and the special caracteres in the comments my application worked.
Try this.
-
8. Re: NPE in ComponentDescription$DefaultFirstConfigurator
shelleyb Aug 19, 2011 5:05 PM (in response to shelleyb)The problem with my application was a misconfigured filter-class that referenced a class that was not available in the EAR. This was due to a misconfiguration in my EAR, although the exception throw during deployment was quite vague.
15:39:44,501 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC00001: Failed to start service jboss.deployment.subunit."server-enterprise-appliance-test-app-1.2.2-SNAPSHOT-exodus-badf.ear"."server-enterprise-appliance-test-web.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."server-enterprise-appliance-test-app-1.2.2-SNAPSHOT-exodus-badf.ear"."server-enterprise-appliance-test-web.war".INSTALL: Failed to process phase INSTALL of subdeployment "server-enterprise-appliance-test-web.war" of deployment "server-enterprise-appliance-test-app-1.2.2-SNAPSHOT-exodus-badf.ear" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765) at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26] at java.lang.Thread.run(Thread.java:662) [:1.6.0_26] Caused by: java.lang.NullPointerException at org.jboss.as.ee.component.ComponentDescription$DefaultFirstConfigurator.configure(ComponentDescription.java:532) at org.jboss.as.ee.component.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:65) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) ... 5 more
Also, unlike the cause for Jean, my applications successfully deploy and start with comments in the web.xml. In fact, I even pasted the exact same snippet of code provided in the previous comment, and my Java EE 5 application deployed successfully to JBoss AS 7.0.1.Final.
EDIT: I did not see Jean Baldessar's latest response before posting this reply, so I apologize for a bit of duplication.
-
9. Re: NPE in ComponentDescription$DefaultFirstConfigurator
jefimm Aug 20, 2011 12:58 PM (in response to jaikiran)I have the same problem with the 7.0.1 final
The error is:
19:40:36,187 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.unit."as3.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."as3.war".INSTALL: Failed to process phase INSTALL of deployment "as3.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
Caused by: java.lang.NullPointerException
at org.jboss.as.ee.component.ComponentDescription$DefaultFirstConfigurator.configure(ComponentDescription.java:532)
at org.jboss.as.ee.component.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:65)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 5 more
Following this thread I have removed everything from web.xml:
<?xml version="1.0" encoding="UTF-8"?>
<web-app version="3.0" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd">
<distributable/>
</web-app>
I have servlets that are configured using annotations, filters and listeners.
-
10. Re: NPE in ComponentDescription$DefaultFirstConfigurator
jaikiran Aug 24, 2011 12:25 AM (in response to jefimm)Please attach a application which reproduces this, so that we can fix this issue.
-
11. Re: NPE in ComponentDescription$DefaultFirstConfigurator
mtpettyp Aug 24, 2011 12:52 PM (in response to jaikiran)This is a bare bones WAR with a web.xml that has a Servlet class that doesn't exist. The same error occurs. It would be nice to get a little more information in the logging about why the deployment failed.
-
war-error.war 453 bytes
-
-
12. Re: NPE in ComponentDescription$DefaultFirstConfigurator
jefimm Aug 24, 2011 3:07 PM (in response to jaikiran)Unfortunately this is commercial app and I do not have the permission to do this.
Are there any additonal logs that can be turned on to help?
-
14. Re: NPE in ComponentDescription$DefaultFirstConfigurator
tc7 Sep 27, 2011 12:30 AM (in response to jaikiran)I get the same error (using JBoss 7.0.1.Final) if I simply modify a custom TLD (war/WEB-INF/mytype.tld) such that the referenced tag class is invalid, eg:
<tag>
<name>badtag</name>
<tagclass>com.myapp.type.BADTag</tagclass>
<info>Demonstrates error</info>
<attribute>
<name>id</name>
<required>false</required>
<rtexprvalue>true</rtexprvalue>
</attribute>
..
</tag>
I had a reference to an unused tag element that caused this error - took me ages to find the problem.
14:23:37,015 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.subunit."MyApp.ear"."MyApp.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."MyApp.ear"."MyApp.war".INSTALL: Failed to process phase INSTALL of subdeployment "MyApp.war" of deployment "MyApp.ear"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
Caused by: java.lang.NullPointerException
at org.jboss.as.ee.component.ComponentDescription$DefaultFirstConfigurator.configure(ComponentDescription.java:532)
at org.jboss.as.ee.component.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:65)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 5 more
Would be nice if it said: Invalid tag [badtag] detected in TLD: mytype.tld ...
etc.