[
https://issues.jboss.org/browse/WFCORE-3937?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on WFCORE-3937:
------------------------------------------
[~jmesnil] Stephen's technique for cleaning up lessens my enthusiasm for my
"--no-history option" suggestion quite a lot, as it seems like a better
technique for cleaning since it eliminates other FS modifications as well beyond the
config history.
Error when running configured wildfly
-------------------------------------
Key: WFCORE-3937
URL:
https://issues.jboss.org/browse/WFCORE-3937
Project: WildFly Core
Issue Type: Bug
Components: Management
Affects Versions: 5.0.0.Final
Reporter: Stephen Buergler
Assignee: Jeff Mesnil
Priority: Minor
Attachments: Dockerfile
08:32:20,676 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0056: Could
not rename /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current to
/opt/jboss/wildfly/standalone/configuration/standalone_xml_history/20180619-083220673:
java.nio.file.DirectoryNotEmptyException:
/opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current
...
08:50:08,531 WARN [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0414: Could
not create a timestamped backup of current history dir
/opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current, so it may
still include versions from the previous boot.
To reproduce:
docker build -t testing .
docker run --rm -it testing
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)