JBoss cannot find deployed content even though it exists in the filesystem

[kclair-rei]

Hello,

We encountered this error on one of our recent deploys:

16:19:52,221 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("deployment" => "app-group-1-

online-web.war")]) - failure description: "JBAS018717: No deployment content with hash 42c8cd4ec3f01732a8506fe2a1532af16d003b29 is available in the deployment content repository for deployment '

app-group-1-online-web.war'. This is a fatal boot error. To correct the problem, either restart with the --admin-only switch set and use the CLI to install the missing content or remove it f

rom the configuration, or remove the deployment from the xml configuration file and restart."

However, this file exists in the filesystem with the correct permissions:

ls -l /usr/share/jbossas/domain/data/content/

drwxr-xr-x. 3 jboss jboss 4096 Jul  8 16:19 42

ls -l /usr/share/jbossas/domain/data/content/42/

drwxr-xr-x. 2 jboss jboss 4096 Jul  8 16:19 c8cd4ec3f01732a8506fe2a1532af16d003b29

ls -l /usr/share/jbossas/domain/data/content/42/c8cd4ec3f01732a8506fe2a1532af16d003b29/

-rw-r--r--. 1 jboss jboss 66155520 Jul  8 16:19 content

I am also able to list the contents of the zipped file with no problem when logged in as the jboss user, so I know the zip file is not corrupt.

I also checked the auditlog, and it does not seem to be an selinux issue.

We are not having any issues with any other deployment content, just this specific content.

Is there somewhere else that JBoss is looking to confirm the existence of the content??

Thanks for any thoughts.

[jaikiran]

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.

[wdfink]

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.

[kclair-rei]

We are using EAP 6.1.0 running in domain mode.  We deployed the content using the native management java API [1] 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>

https://docs.jboss.org/author/display/AS71/The+native+management+API

[kclair-rei]

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.

[meriamjabl]

Hi,

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

Remove :

<deployment name="app-group-1-online-web.war" runtime-name="app-group-1-online-web.war">
   <content sha1="dcb4683c68f8ef7f07383bc7e0e0d3f039632c5f"/>
</deployment>

[anchalsachdev]

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.