ERROR [org.jboss.as.controller.management-operatio

Question

• JBoss Bootstrap Environment

• JBOSS_HOME: C:\Program Files (x86)\jboss-as-7.1.1.Final

• JAVA: C:\Program Files (x86)\Java\jdk1.6.0_45\bin\java

• JAVA_OPTS: -XX:+TieredCompilation -Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInt =3600000 -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djboss.server.default.config=standalone.xml

---

Getting this error while starting jBoss...

17:14:57,087 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA
17:14:57,517 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA
17:14:57,637 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
17:14:59,791 ERROR [org.jboss.as.controller.management-operation] Operation ("add") failed - address: ([("deployment" => "mysql-connector-java-5.1.24-bin.jar")]) - failur
cription: "JBAS018717: No deployment content with hash a7d599d73b86a928303909b9be7573a4ea0ed28e is available in the deployment content repository for deployment 'mysql-co
or-java-5.1.24-bin.jar'. 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 conten
remove it from the configuration, or remove the deployment from the xml configuraiton file and restart.."
17:14:59,801 FATAL [org.jboss.as.server] JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
17:14:59,821 INFO  [org.jboss.as] JBAS015950: JBoss AS 7.1.1.Final "Brontes" stopped in 9ms
Press any key to continue . . .

Answer 1

A bit late, but an answer might be helpful for others facing the same problem, so here goes.

As the error indicates a deployment is defined in the configuration, but the content is missing (in this case a MySQL JDBC driver).

To fix such an error you have to install the missing deployment or remove it from the configuration (in this case standalone.xml).

If you read the error description, it explains both the problem and possible solutions pretty well.

To correct the problem, either restart with the --admin-only switch set and use the CLI to install the missing conten remove it from the configuration, or remove the deployment from the xml configuraiton file and restart..