[infinispan-issues] [JBoss JIRA] (ISPN-1749) log4j.configuration system property cannot be set

[Manik Surtani (JIRA)]

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

Manik Surtani commented on ISPN-1749:
-------------------------------------

@David - feel like contributing a patch to this?
                
> log4j.configuration system property cannot be set
> -------------------------------------------------
>
>                 Key: ISPN-1749
>                 URL: https://issues.jboss.org/browse/ISPN-1749
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Configuration
>    Affects Versions: 5.1.0.CR4
>         Environment: Unix
>            Reporter: David van Balen
>            Assignee: Manik Surtani
>              Labels: configuration, infinispan, log4j, logging
>             Fix For: 5.1.0.FINAL
>
>
> Although the startServer.sh script provides a way to specify custom system properties, via the JVM_PARAMS environment variable, it is not possible to specify a different log4j configuration file through the log4j.configuration system property because it will be overridden in functions.sh (see script snippet below, starting at line 154 of functions.sh). I think the portion of functions.sh that sets the location of the log4j configuration file should only execute if the user hasn't provided their own location.
>   # Log4J config path needs path conversion in Cygwin
>   if $CYGWIN; then
>     LOG4J_CONFIG=`cygpath -w "${ISPN_HOME}/etc/log4j.xml"`
>   else
>     LOG4J_CONFIG=${ISPN_HOME}/etc/log4j.xml
>   fi
>   START_ARGS=( "${START_ARGS[@]}" "-Dlog4j.configuration=file:///$LOG4J_CONFIG" )

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira