log4j.properties: FileNotFoundException

[Haritha Gorijavolu]

I am using log4j for logging.I am using a configuration file called log4j.properties. I have placed it in the class path. The program is running fine and events are being printed to the output log.
Yet, when I run the program in eclipse in tomcat server runtime, it is giving the following errors on the console:

log4j:ERROR Could not read configuration file [log4j.properties].
java.io.FileNotFoundException: log4j.properties (The system cannot find the file specified)
//stack trace
//stack trace
//stack trace
//stack trace
log4j:ERROR Ignoring configuration file [log4j.properties].

Can any one explain why these errors are printed on the console. Thanks in advance.

The following is my log4j.properties file

log4j.rootCategory=DEBUG, R  
   
# File   
log4j.appender.R=org.apache.log4j.RollingFileAppender   
log4j.appender.R.File=C:/Users/haritha.g/Desktop/log4j.log   
  
# Control the maximum log file size   
log4j.appender.R.MaxFileSize=100KB   
  
# Archive log files (one backup file here)   
log4j.appender.R.MaxBackupIndex=1  
  
log4j.appender.R.layout=org.apache.log4j.PatternLayout   
  
log4j.appender.R.layout.ConversionPattern=[%d{ISO8601}]%5p%6.6r[%t]%x - %C.%M(%F:%L) - %m%n   

The following is the code I wrote to use it.

static Logger logger = Logger.getLogger(MyClass.class.getName());
PropertyConfigurator.configure("log4j.properties");

[Jay Dilla]

I'm having the same problem, except mine says no appender. even though i have defined and placed the property file in the class path on the unix box. I don't have that property configure line that you have though....I'll try that.

[Paul Clapham]

Haritha, if you really have your configuration file in the classpath, then just take out this line:

PropertyConfigurator.configure("log4j.properties");  

Not only is it unnecessary, it's the source of the problem as it tells log4j to look in your current working directory for the configuration file. Presumably your current working directory isn't part of your classpath.

[Sanjeev P Kulkarni]

Paul Clapham wrote:Haritha, if you really have your configuration file in the classpath, then just take out this line:

PropertyConfigurator.configure("log4j.properties");  

Not only is it unnecessary, it's the source of the problem as it tells log4j to look in your current working directory for the configuration file. Presumably your current working directory isn't part of your classpath.

If your log4j.properties file is in the top most of the directory i.e src/log4j.properties then you don't have to use PropertyConfigurator.configure("log4j.properties"); log4j will automatically searches for that file. hope this will help.