Friday, 16 January 2009

Debugging log4j itself

Problem: You cannot find out which log4j.properties file is used.

Try running VM with parameter
-Dlog4j.debug

You'll get info about log4j properties in console.

See: http://logging.apache.org/log4j/1.2/manual.html
Posted by Kris at 10:15
Labels: ,

1 comment:

Laurentiu Delcea said...

This works great, I had a project with multiple maven modules and I was not sure what properties log4j would load.

Thank you!

28 August 2014 at 10:52

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts

  • Apache Archiva admin account locked
    (Archiva 1.1.3 with default Derby database) Many times I have had this problem. It's time to note the solution here, so I would not wa...
  • velocity.log Permission denied
    (within JadaSite 2.03 using Apache Valocity 1.5) I got a lot of Permission denied stacktraces for velocity.log within my catalina.out . ...
  • Debugging log4j itself
    Problem: You cannot find out which log4j.properties file is used. Try running VM with parameter -Dlog4j.debug You'll get info about log4...