]
James Perkins resolved WFLY-2643.
---------------------------------
Resolution: Won't Fix
There is a workaround to use the {{-Djboss.server.log.dir}} system property via the
command line or via the {{standalone.conf(.bat)}}. I'd rather not make any changes to
the scripts if possible as we've had issues with them recently.
Pass the jboss.server.log.dir parameter to the global system
properties
-----------------------------------------------------------------------
Key: WFLY-2643
URL:
https://issues.jboss.org/browse/WFLY-2643
Project: WildFly
Issue Type: Enhancement
Components: Logging, Server
Affects Versions: JBoss AS7 7.1.1.Final, 8.0.0.Beta1
Environment: All
Reporter: Stian Lund
Priority: Optional
Labels: jbossas, logging, wildfly
In standalone/domain start scripts (standalone.sh/bat) the value of environment variable
JBOSS_LOG_DIR is checked for:
{code}
# determine the default log dir, if not set
if [ "x$JBOSS_LOG_DIR" = "x" ]; then
JBOSS_LOG_DIR="$JBOSS_BASE_DIR/log"
fi
{code}
However, this is not actually used to set the value of Java property
jboss.server.log.dir.
{code}
-Djboss.home.dir="$JBOSS_HOME"
-Djboss.server.base.dir="$JBOSS_BASE_DIR"
"$SERVER_OPTS"
{code}
(It should be set at the same place)
This leads Jboss/Wildfly/EAP to assume the default value of $JBOSS_BASE_DIR/log.
This is a problem for those who want to override the location of the server.log files.