2

We use wildfly 10.x as an application server. Our setup is much restrictive. So the AS user is not allowed to write to jboss.server.base.dir/configuration/ but at startup it wants to write the standalone.xml.tmp file to that location. Is there a way to change the location for that file to jboss.server.tmp.dir?

I added also wildfly8 as a tag because it may be also a interesting thing for that version.

Christian Meißner
  • 131
  • 9
  • 1
    Wildfly allow you change the configuration location directory by setting the `jboss.domain.config.dir` jvm propertie, but not provide any direct way to change location of `standalone_xml_history` directory. You can try change entire `jboss.domain.config.dir` to a new location o another thing that I think you can try is create a symlink for the `standalone_xml_history`. – Federico Sierra Jul 07 '17 at 15:40
  • The symlink aproach is unfortunately not a solution because wildfly tries to delete the standalone.xml.tmp file. – Christian Meißner Jul 10 '17 at 05:19
  • My recommendation was create a symlink for `standalone_xml_history` directory, not for files inside this. – Federico Sierra Jul 10 '17 at 13:53
  • Ah, wildfly 10 generates files directly under configuration, not standalone_xml_history. This is the main cause. – Christian Meißner Jul 10 '17 at 13:56
  • Yes you are right, the standalone.xml.tmp is created in base config directory. – Federico Sierra Jul 10 '17 at 14:00

1 Answers1

0

If you don't want to change the standalone.xml during runtime then you can call:

standalone.bat --read-only-server-config=standalone.xml

That won't touch any file in your configuration folder. Even the logging.properties is not touched, if the content is already matching the standalone.xml.

Tobias Liefke
  • 101
  • 2