]
ehsavoie Hugonnet commented on WFCORE-1330:
-------------------------------------------
Hum, the war should be read and written by the user that is running Wildfly. Now it all
depends on what rights does this WildFly user have. He should be able to write in the
WildFly directories since you are in /opt I'm wondering what you have set.
Deployment error after reboot [WFLYSRV0137]
-------------------------------------------
Key: WFCORE-1330
URL:
https://issues.jboss.org/browse/WFCORE-1330
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 1.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: ehsavoie Hugonnet
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.