[
https://issues.jboss.org/browse/WFLY-2643?page=com.atlassian.jira.plugin....
]
James Perkins commented on WFLY-2643:
-------------------------------------
I'm positive :). The reason the shell variable is checked is because a valid log
directory is needed to define the property for the server.log. Look at the property
{{-Dorg.jboss.boot.log.file=$JBOSS_LOG_DIR/server.log}}. That is used at boot time in the
{{logging.properties}} (at first boot at this point) to determine the file to use for the
log handler.
Adding the system property is the correct way just as it would be for the
{{jboss.server.data.dir}} or {{jboss.server.tmp.dir}} directories. You could add
{{-Djboss.server.log.dir=$LOG_DIR}} to the {{standalone.conf}}.
JBOSS_LOG_DIR is checked but not used to set jboss.server.log.dir
-----------------------------------------------------------------
Key: WFLY-2643
URL:
https://issues.jboss.org/browse/WFLY-2643
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Logging, Server
Affects Versions: JBoss AS7 7.1.1.Final, 8.0.0.Beta1
Environment: All
Reporter: Stian Lund
Assignee: James Perkins
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira