There is a possible race when restoring persistent bundles. The FrameworkActivateProcessor may want to activate the framework before FrameworkBootstrapService.start() completes. [0m [31m14:33:49,853 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.unit."de.xxx.yyy.data.services.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."de.xxx.yyy.data.services.jar".PARSE: JBAS018733: Failed to process phase PARSE of deployment "de.xxx.yyy.data.services.jar" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA.jar:1.0.4.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA.jar:1.0.4.GA] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_05] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_05] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_05] Caused by: java.lang.NullPointerException at org.jboss.as.osgi.service.FrameworkActivator.activate(FrameworkActivator.java:76) at org.jboss.as.osgi.deployment.FrameworkActivateProcessor.deploy(FrameworkActivateProcessor.java:72) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4]
Thomas Diesler <thomas.diesler> updated the status of jira JBEAP-10 to Resolved
Related https://issues.jboss.org/browse/JBEAP-10 and PR https://github.com/jbossas/jboss-eap/pull/123 have been closed. Closing this as well.