In this post, we are going to
discuss the deployment problem that prevents JBoss Server to start properly.
The below defined error usually
occurs when we delete directory standalone\data or domain\data and then try to
redeploy the same application war. The JBoss server unable to delete entries
defined in standalone.xml/domain.xml with the same hash for the deployed
application.
06:02:24,774 ERROR
[org.jboss.as.controller.management-operation] (Controller Boot Thread)
JBAS014612: Operation ("add") failed - address:
([("deployment" => "abc.ear")]) - failure description:
"JBAS018717: No deployment content with hash
545ac26ed6a31ef41d749d5228669eb6858bb345 is available in the deployment
content repository for deployment 'abc.ear'. 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 from the configuration,
or remove the deployment from the xml configuration file and restart."
06:02:24,785 FATAL [org.jboss.as.server]
(Controller Boot Thread) JBAS015957: Server boot has failed in an
unrecoverable manner; exiting. See previous messages for details.
|
The domain.xml looks
like below:
In Deployments definition:
<deployment
name="abc.ear" runtime-name="abc.ear">
<content sha1="545ac26ed6a31ef41d749d5228669eb6858bb345"/>
</deployment>
|
Server –group Definition:
<server-group name="abc-group" profile="abc">
<socket-binding-group ref="ha-sockets"/>
<deployments>
<deployment name="abc.ear" runtime-name="abc.ear"/>
<deployment
name="ojdbc6.jar" runtime-name="ojdbc6.jar"/>
</deployments>
</server-group>
|
Removing the entries manually for the application having
defined hash from domain.xml and then restart the DC and application server.
No comments:
Post a Comment