Best Practice on Configuring Log4j Properties Path

I am using Log4j in my applications. log4j.properties is placed in a Jar which is in classpath. This configuration file is being used and works fine most of the times.

But sometimes, the logging statements that are getting generated are not as per the configuration file.

My understanding is, this is because the properties file is fetched from the class path. Whatever first properties file is, is fetched and used by log4j. Thus sometimes we get the logging statements different fro开发者_如何学Cm what is configured in properties file.

In case, the above reason is true, then I think, we need to specify the configuration file specifically by one of the following ways:

1. Specify using System Properties : -Dlog4j.configuration=log4j.properties
2. Initializing Log4jInit servlet.

Please suggest which could be the better approach.

In my application I am using ${user.home} dir to store log4j.properties and using ant we are reading it. it will be platform independent. also you can pass one with build in classpath but reading from ${user.home} is better approach, You or any non technical person can easily access it.

also you can use

Dynamic Log File Location

Many people complain that Log4j forces you to hard-code the location where your logs will be kept. Actually, it is possible to dynamically choose the log-file location, especially if you use the ${log.dir} property substitution technique above. Here's how:

String dynamicLog = // log directory somehow chosen...
Properties p = new Properties( Config.ETC + "/log4j.properties" );
p.put( "log.dir", dynamicLog ); // overwrite "log.dir"
PropertyConfigurator.configure( p );

Also See

• Effective logging practices ease enterprise development
• Log4j Best practices

When searching for items on the classpath the first instance of file with a matching name is used. So add your .jar to the front.

set CLASSPATH=myfile.jar;%CLASSPATH%