This week's book giveaway is in the Reactive Progamming forum. We're giving away four copies of Reactive Streams in Java: Concurrency with RxJava, Reactor, and Akka Streams and have Adam Davis on-line! See this thread for details.
http://logging.apache.org/log4j/1.2/manual.html (search text for "by default, the root logger" or default, or whatever). Since you don't define a log level, it's just going to use that, hence TRACE-level log statements won't be logged. So "what gives" is that you've not configured Log4J correctly based on what you want to see.
posted 9 years ago
i meant that it DOES gets logged, but it gets logged as DEBUG, and not as trace. i thought at first i somehow have the wrong commons version (in commons 1.0.x) it used to do just that, turn every trace call into debug call, as older log4j's didn't support trace, but even this simplest code still turns into debug.
Are you sure the correct version of those libraries are being used in the runtime? You can add -verbose:class to the JVM arguments, which will print out the information of the jars which are being used to load the classes. That might show you whether a stray jar in the classpath is being picked up.