[jboss-jira] [JBoss JIRA] (WFLY-2249) NPE during redeployment of a war
Juergen Zimmermann created WFLY-2249:
----------------------------------------
Summary: NPE during redeployment of a war
Key: WFLY-2249
URL: https://issues.jboss.org/browse/WFLY-2249
Project: WildFly
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 8.0.0.Beta1
Reporter: Juergen Zimmermann
Assignee: Scott Marlow
When I redeploy an already running war, then I get the following NPE. The (re-) deployment
is done via the Maven plugin org.jboss.as.plugins:jboss-as-maven-plugin:7.4.Final. It
looks like the redployment was successful anyway. Hmm...
{code}
ERROR [org.jboss.msc.service.fail] MSC000001: Failed to start service
jboss.deployment.unit."shop.war".PARSE: org.jboss.msc.service.StartException in
service jboss.deployment.unit."shop.war".PARSE: JBAS018733: Failed to process
phase PARSE of deployment "shop.war"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166)
[wildfly-server-8.0.0.Beta1.jar:8.0.0.Beta1]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1944)
[jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1877)
[jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[rt.jar:1.7.0_40]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[rt.jar:1.7.0_40]
at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_40]
Caused by: java.lang.NullPointerException
at
org.jboss.as.jpa.processor.PersistenceUnitParseProcessor.handleWarDeployment(PersistenceUnitParseProcessor.java:126)
at
org.jboss.as.jpa.processor.PersistenceUnitParseProcessor.deploy(PersistenceUnitParseProcessor.java:83)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159)
[wildfly-server-8.0.0.Beta1.jar:8.0.0.Beta1]
... 5 more
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira