An issue that could result in a NullPointerException has been resolved in this release of JBoss EAP 6. The exception could present when a deployment partially restarted some data structures that were required have already been cleaned up to save memory (for example, when a dependency was replaced). This issue would prevent the redeployment from completing. To address this issue, partial redeployments are no longer allowed in this release of the product. If a dependency is replaced the deployment is now completely restarted and the exception no longer presents.
If you have a deployment that dependends on another deployment (either using inter deployment dependencies or a class loading dependency) and you replace the dependee deployment then the dependent deployment will fail to restart.
Stuart Douglas <email@example.com> made a comment on jira AS7-6761
This is now resolved for non OSGi deployments. At the moment I can't see any way to achieve the desired OSGI behaviour without a redesign of how DUP's work.
Brian Stansberry <firstname.lastname@example.org> made a comment on jira AS7-6761
I'm moving this out of "Pull Request Sent" status but not to "Resolved" because AIUI the fix did not fully resolve the reported issue. I'll leave it to you guys to sort out what the next step is.
This is resolved for non-OSGi deployments. I think we should resolve this issue and create a new one for the OSGi problems, as the OSGi issue is not so much caused by dependency changes but rather by explicit start/stop operations on the bundle.
<module name="deployment.clusterbench.war" />
Triggers in EAP 6.3:
Unregister web context: /clusterbench
Unregister web context: /SessionTest
Deployment restart detected for deployment SessionTest.war, performing full redeploy instead.
Register web context: /clusterbench
Register web context: /SessionTest
Triggers in EAP 6.2:
MSC000001: Failed to start service jboss.deployment.unit."SessionTest.war".FIRST_MODULE_USE:
Reformatted docs text and marked for inclusion in 6.3.0 Release Notes.
Brad Maxwell <email@example.com> updated the status of jira WFLY-1363 to Resolved