[jboss-jira] [JBoss JIRA] (WFCORE-3937) Error when running configured wildfly
[
https://issues.jboss.org/browse/WFCORE-3937?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on WFCORE-3937:
------------------------------------------
This is failing in a call to Files.move, which has this javadoc:
{code}
* When invoked to move a
* directory that is not empty then the directory is moved if it does not
* require moving the entries in the directory. For example, renaming a
* directory on the same {@link FileStore} will usually not require moving
* the entries in the directory. When moving a directory requires that its
* entries be moved then this method fails (by throwing an {@code
* IOException}).
{code}
The directory won't be empty but it's strange that there's a need to move the
entries in the dir, i.e. the two paths should in the same FileStore.
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 -ttesting .
docker run --rm -it testing
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)