log4j.properties system variable not loading correctly

[msegreti4355]

I am using log4j 1.2.17 and deploying my application using Jboss EAP 6.2 GA. My log4j is configured using a log4j.properties file that I configured. I wanted output of a DailyRollingFileAppender to go to a directory based on a system variable. So I have it set up like this:

log4j.appender.MAIN.File=${EAP_HOME}/standalone/log/system.log

In the VM Arguments of the server configuration I have:

-DEAP_HOME=${EAP_HOME}

Where EAP_HOME is an Environment Variable I set up.

My Problem is that whenever I try and log, my output goes to EAP_HOME/bin/standalone/log/system.log

I am not sure why it is going to the bin directory when that is not specified anywhere in my settings.

I want it to be in EAP_HOME/standalone/log/system.log

Any ideas?

[jamezp]

Have you tried using ${jboss.server.log.dir} instead? That should evaluate to the correct path.

--

James R. Perkins

[msegreti4355]

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.

[jaikiran]

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).

[jamezp]

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

[jaikiran]

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.