This week's book giveaway is in the OCAJP forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide 1Z0-808 and have Jeanne Boyarsky & Scott Selikoff on-line! See this thread for details.
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
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.
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 ]