JBoss Deployment War Error on Startup
We take a look at how to quickly solve the frustrating error that occurs when a JBoss server doesn't start up properly.
Join the DZone community and get the full member experience.Join For Free
JBoss Server Not Starting
In this post, we are going to discuss the
deployment problem that prevents
JbossServer from starting properly.
Error While Starting JBoss Server (in Domain Mode)
JbossServer logs in this case looks like below:
10:16:57,337 INFO [org.jboss.modules] JBoss Modules version 1.1.3.GA-redhat-1
10:16:57,498 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA-redhat-2
10:16:57,686 INFO [org.jboss.as] JBAS015899: JBoss EAP 6.0.1.GA
(AS 7.1.3.Final-redhat-4) starting
10:16:58,310 INFO [org.jboss.as.server.deployment.scanner] JBAS015014: Re-attempting failed deployment abc.warploy
10:16:58,340 INFO [org.jboss.as.server.deployment.scanner] JBAS015003: Found abc.war in deployment directory. To trigger deployment create a file called abc.war.dodeploy
10:16:58,348 ERROR [org.jboss.as.controller.management-operation] JBAS014613: Operation ("add") failed - address: ([("deployment" => "abc-ABC.0.0.21.war")]) - failure description: "JBAS018717: No deployment content with hash28c2ce34057a6bd5ebf2c28f9d114814faa66b8a is available in the deployment content repository for deployment 'abc-ABC.0.0.21.war'.
This is a fatal boot error. To correct the problem, either restart with the --admin-onlyswitch set and use the CLI to install the missing content or remove it from theconfiguration, or remove the deployment from the xml configuraiton file and restart."
10:16:58,351 ERROR [org.jboss.as.server.deployment.scanner] JBAS014654: Composite operation was rolled back
10:16:58,351 FATAL [org.jboss.as.server] JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
10:16:58,358 INFO [org.jboss.as] JBAS015950: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) stopped in 3ms
error also occurs when we delete the directory standalone\data.. and then try to
redeploy the same application to a
Jbossserver is unable to delete entries defined in
standalone.xml with the same
hash for the
standalone.xml looks like the below:?
Removing the entries manually for the
application defined in
hash solved this problem and
Jbossserver will start successfully without error.
Published at DZone with permission of Muhammad Ali Khojaye, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.