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

[Stian Lund (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-2643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930925#comment-12930925 ] 

Stian Lund edited comment on WFLY-2643 at 12/12/13 1:45 PM:
------------------------------------------------------------

Are you sure about that? There would be little point in checking for the value being set, if it is only the Java property that controls the setting.

In addition, the value of for instance JBOSS_BASE_DIR is checked for in the same way but is also used to set a property on launch. I would be interested to know the reasoning behind LOG_DIR not being considered to have the same use?

The reason I ask, is I would like to have LOG_DIR set in init (it already wraps the location of CONSOLE_LOG), and not have to code the property into standalone.conf as well, which is not very elegant IMO.

                
      was (Author: pathduck):
    Are you sure about that? There would be little point in checking for the value being set, if it is only the Java property that controls the setting.

In addition, the value of for instance JBOSS_BASE_DIR is checked for in the same way but is also used to set a property on launch. I would be interested to know the reasoning behind LOG_DIR not being considered to have the same use?

The reason I ask, is I would like to have LOG_DIR set in init (it already wraps the location of CONSOLE_LOG), and not have to code the property into standalone.conf as well, whixh is not very elegant IMO.

                  
> 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