[jboss-jira] [JBoss JIRA] (WFLY-6131) Cannot reconfigure standard paths
Rich DiCroce created WFLY-6131:
----------------------------------
Summary: Cannot reconfigure standard paths
Key: WFLY-6131
URL: https://issues.jboss.org/browse/WFLY-6131
Project: WildFly
Issue Type: Bug
Affects Versions: 10.0.0.Final
Reporter: Rich DiCroce
Assignee: Jason Greene
The [WildFly 10 Admin
Guide|https://docs.jboss.org/author/display/WFLY10/Admin+Guide#AdminGuide...] says that
it should be possible to change the location of various directories that WildFly uses.
Specifically, it states that
{quote}
WildFly automatically provides a number of standard paths without any need for the user to
configure them in a configuration file:
jboss.home.dir - the root directory of the WildFly distribution
user.home - user's home directory
user.dir - user's current working directory
java.home - java installation directory
jboss.server.base.dir - root directory for an individual server instance
jboss.server.config.dir - directory the server will use for configuration file
storage
jboss.server.data.dir - directory the server will use for persistent data file
storage
jboss.server.log.dir - directory the server will use for log file storage
jboss.server.temp.dir - directory the server will use for temporary file storage
jboss.controller.temp.dir - directory the server will use for temporary file storage
jboss.domain.servers.dir - directory under which a host controller will create the
working area for individual server instances (managed domain mode only)
Users can add their own paths or override all except the first 5 of the above by adding a
<path/> element to their configuration file.
{quote}
I tried setting jboss.server.data.dir as described and got the following error:
{noformat}
17:49:53,753 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught
exception during boot:
org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed
to parse configuration
at
org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:131)
[wildfly-controller-2.0.10.Final.jar:2.0.10.Final]
at org.jboss.as.server.ServerService.boot(ServerService.java:356)
[wildfly-server-2.0.10.Final.jar:2.0.10.Final]
at
org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:299)
[wildfly-controller-2.0.10.Final.jar:2.0.10.Final]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_60]
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[50,9]
Message: WFLYCTL0173: jboss.server.data.dir is reserved
at org.jboss.as.server.parsing.PathsXml.parsePath(PathsXml.java:131)
[wildfly-server-2.0.10.Final.jar:2.0.10.Final]
at org.jboss.as.server.parsing.PathsXml.parsePaths(PathsXml.java:105)
[wildfly-server-2.0.10.Final.jar:2.0.10.Final]
at org.jboss.as.server.parsing.CommonXml.parsePaths(CommonXml.java:185)
[wildfly-server-2.0.10.Final.jar:2.0.10.Final]
at
org.jboss.as.server.parsing.StandaloneXml_4.readServerElement(StandaloneXml_4.java:227)
[wildfly-server-2.0.10.Final.jar:2.0.10.Final]
at org.jboss.as.server.parsing.StandaloneXml_4.readElement(StandaloneXml_4.java:141)
[wildfly-server-2.0.10.Final.jar:2.0.10.Final]
at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:103)
[wildfly-server-2.0.10.Final.jar:2.0.10.Final]
at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:49)
[wildfly-server-2.0.10.Final.jar:2.0.10.Final]
at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110)
[staxmapper-1.2.0.Final.jar:1.2.0.Final]
at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69)
[staxmapper-1.2.0.Final.jar:1.2.0.Final]
at
org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:123)
[wildfly-controller-2.0.10.Final.jar:2.0.10.Final]
... 3 more
{noformat}
Indeed, examining the source for PathsXml reveals that almost all of the paths listed in
the documentation (not just the first 5) are considered restricted and cannot be changed.
I'm not sure if this is actually a bug or if the documentation is just wrong. If the
former, this issue belongs in WFCORE.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)