[
https://issues.jboss.org/browse/WFLY-6500?page=com.atlassian.jira.plugin....
]
Michael Peoples commented on WFLY-6500:
---------------------------------------
The Camunda fix is for 7.6, which is still in Alpha testing. I'll see about doing a
manual setup. And get back to you.
I'm not sure this condition is consistently reproducible, unless someone has a
specific sequence of steps to cause it. Examination of the logs showed nothing more than
the new deployment being rejected because a similar deployment was already registered.
Even switching version numbers didn't help. However, I'm not sure what
circumstances are required to reproduce the server crash.
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: Jason Greene
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)