[jboss-jira] [JBoss JIRA] (WFLY-6061) Deployment error after reboot [WFLYSRV0137]

Tobi Tobias (JIRA) issues at jboss.org
Mon Jan 25 04:55:00 EST 2016


Tobi Tobias created WFLY-6061:
---------------------------------

             Summary: Deployment error after reboot [WFLYSRV0137]
                 Key: WFLY-6061
                 URL: https://issues.jboss.org/browse/WFLY-6061
             Project: WildFly
          Issue Type: Bug
          Components: ConfigAdmin
    Affects Versions: 9.0.2.Final
         Environment: Ubuntu 14.04 LTS 64bit, jre-1.8.0_65
Several deployed (JavaEE) web applications including non XA datasources that connect to a MySQL instance.
            Reporter: Tobi Tobias
            Assignee: Thomas Diesler
            Priority: Critical


I have a working configuration on wildfly 9.0.2 final with several web applications (JavaEE).

After a couple of days, I deployed another war file via jboss CLI. This application worked correctly and no deployment error occurred.
But if I restart the server now, I get following error message:
10:36:01,893 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "MM-Controller-0.1.0-SNAPSHOT.war")]) - failure description: "WFLYSRV0137: No deployment content with hash 966847a6f5f5bf8c3470f07ea9e65b7bbcdcd7b7 is available in the deployment content repository for deployment 'MM-Controller-0.1.0-SNAPSHOT.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 from the configuration, or remove the deployment from the xml configuration file and restart."
10:36:01,990 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.

I reproduced this at least 30 times - even with different jars. I always get this error. The server works fine as long as I don't reboot.
The only way to fix the configuration is to manually remove the deployments from the standalone.xml.
But this is not an option for me as I want to have the wildfly running as production server where I have several automatic deployments every day.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the jboss-jira mailing list