[jboss-jira] [JBoss JIRA] (WFLY-2643) JBOSS_LOG_DIR is checked but not used to set jboss.server.log.dir

[James Perkins (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-2643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Perkins resolved WFLY-2643.
---------------------------------

    Resolution: Won't Fix


The intention of the {{JBOSS_LOG_DIR}} variable in the scripts is for internal usage in the script only. To change the log directory you _must_ use the {{jboss.server.log.dir}} system property. You can pass it from the command line with {{-Djboss.server.log.dir=your/directory}} or add the same property 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