-
1. Re: log4j.properties system variable not loading correctly
jamezp Jul 29, 2014 8:04 PM (in response to msegreti4355)1 of 1 people found this helpfulHave you tried using ${jboss.server.log.dir} instead? That should evaluate to the correct path.
--
James R. Perkins
-
2. Re: log4j.properties system variable not loading correctly
msegreti4355 Jul 30, 2014 9:28 AM (in response to jamezp)As it turns out my problem is with the way that the environment variable works. For some reason it is grabbing the string literal $EAP_HOME instead of referencing the environment variable.
-
3. Re: log4j.properties system variable not loading correctly
jaikiran Jul 30, 2014 9:56 AM (in response to msegreti4355)I don't think Log4j replaces those literals with system property values. Such property replacement is a JBoss AS/WildFly specific feature available only for a certain type of files (like deployment descriptors and domain configuration files).
-
4. Re: log4j.properties system variable not loading correctly
jamezp Jul 30, 2014 11:14 AM (in response to jaikiran)It should evaluate system properties the same way WildFly does. Same syntax even, but I'm not sure they allow for a default value.
--
James R. Perkins
-
5. Re: log4j.properties system variable not loading correctly
jaikiran Jul 30, 2014 11:37 AM (in response to jamezp)James Perkins wrote:
It should evaluate system properties the same way WildFly does. Same syntax even, but I'm not sure they allow for a default value.
--
James R. Perkins
I didn't know that. I just googled around and it looks like this feature was introduced in Log4j in 2.x version http://logging.apache.org/log4j/2.x/ whereas Matthew states that he's using 1.2.17 version.
Either way, good to know that log4j now has this support.