[
https://issues.jboss.org/browse/WFLY-6500?page=com.atlassian.jira.plugin....
]
Jason Morgan commented on WFLY-6500:
------------------------------------
Removing the war from the deployment directory after a crash does let the server start
back up. The problem is that wildfly thinks it has 2 versions of the same war loaded, one
through deployment and one through the web console (which gets saved to a hashed
directory). Replacing the war through the webconsole reports success but really
doesn't work on reboot. Instead, this either shouldn't be an option for a war
deployed through the deployment directory or it should actually remove the war in the
deployment.
wildfly-10.0.0.Final deployment crash
-------------------------------------
Key: WFLY-6500
URL:
https://issues.jboss.org/browse/WFLY-6500
Project: WildFly
Issue Type: Bug
Affects Versions: 10.0.0.Final
Reporter: Jason Morgan
Assignee: Tomaz Cerar
Fix For: 10.1.0.Final
Having a war in the deployment directory and then "replacing" a deployment
through the web console causes the server to crash without any logging on restart
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)