Which exact version of the server is this? How did you add/deploy the content and when do you see this exception? What does the deployments section look like in the relevant standalone/domain configuration file.
Do you use the domain mode? If yes there are several places for the content, for domain admin, host admin and each server.
If there are manual changes this error might be happen.
We are using EAP 6.1.0 running in domain mode. We deployed the content using the native management java API  version 7.1.2Final. This method of deploying content has been working for us oherwise, it is just this one deploy that has been failing in this way.
The deployments section of domain.xml on the domain controller looks like this:
<deployments> <deployment name="app-group-1-online-web.war" runtime-name="app-group-1-online-web.war"> <content sha1="42c8cd4ec3f01732a8506fe2a1532af16d003b29"/> </deployment> </deployments> <server-groups> <server-group name="app-group-1" profile="ha-0"> ... <deployments> <deployment name="app-group-1-online-web.war" runtime-name="app-group-1-online-web.war"/> </server-group> </server-groups>
Yes, we are using domain mode. As far as I can tell, the content is being added to /usr/share/jbossas/domain/data/content/ on the domain controller and host controllers. The ls results I pasted in my original posts were from the host controller.
In order to fix this problem you need to go to standalone.xml (or domain.xml ) and remove the missing deployment. In fact while starting JBoss find an deployment entry in standalone.xml but not the war in /deployments.
For more details see this link: http://mariemjabloun.blogspot.com/2014/05/resolve-jboss-startup-failure-due-to.html
<deployment name="app-group-1-online-web.war" runtime-name="app-group-1-online-web.war"> <content sha1="dcb4683c68f8ef7f07383bc7e0e0d3f039632c5f"/> </deployment>
I am facing the same issue. I have my Wildfly 10 server installed on Linux and I am using it in standalone mode. All the data in Wildfly-source-folder/standalone/data/content is getting deleted when I restart the server and the above exception is thrown. It works when I remove the entry for the war file in standalone.xml and start the server. But this cannot be a permanent solution right. How do I manage this situation in Production environment.