Win a copy of Functional Reactive Programming this week in the Other Languages forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

log4j not working with JUnit

 
Barry Andrews
Ranch Hand
Posts: 529
C++ Java Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,
I have a very strange problem. I hope someone else has seen this before. I have a class that uses log4j, and it works fine if I run the class by itself. I use PropertyConfigurator.configure("MyFile.ini"); However, if I run JUnit on this class, I get tons of errors like this:

If I use BasicConfigurator.confiure() in the tested class, then JUnit will run it just fine.
Very strange! Has anyone seen this problem before?
Many thanks to you,
Barry
 
Brian Buckley
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am seeing the identical problem. If anyone knows areason, a solution or a workaround, please post.
Brian
 
Calvin Robol
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
There is a workaround that will work with log4j, however it requires you to rebuild/re-jar JUnit.
In the junit.jar, there is a file called excluded.properties. This lists all the packages you want to exclude from the Junit custom class loader, which I believe is causing the problem with log4j. Just add excluded.9=org.apache.log4j.*
to the list, rebuild junit, and log4j should work fine within your junit tests.
 
Olaf Kittelmann
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I just used the workaround and now the
error with the double class loader is gone.
however, my log4j output is also gone.
I stepped through the log4j code and found that it tries to apply INFO level for my class although the rootlogger and the class explicitly are set to DEBUG level in the logger properties.
I helped myself with system.out statements, but
I am not really happy about it.
thanks,
Olaf
[ January 23, 2003: Message edited by: Olaf Kittelmann ]
 
Henrik Bladh
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I've had the same problem and I solved it by passing "-Dlog4j.ignoreTCL=true" to the jvm.
http://www.mail-archive.com/log4j-dev@jakarta.apache.org/msg02425.html
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic