It is possible that your app might be reading a log4j config file somewhere in a jar. If you want to test, try commenting out your "PropertyConfigurator" line and see if your debug statement in your code still works. My guess is your log4j.properties file isnt on your CLASSPATH. Usually src folders arent on the CLASSPATH unless you add them yourself. If all else fails, try adding the absolute file path of your log4j.properties file to your CLASSPATH.
hth, -Ryan On Tue, Apr 10, 2012 at 7:26 AM, tommmmmm <[email protected]> wrote: > I used it prior to using local path. Didn't work either. Also - the > logger.debug("some > test message"); is pretty much a 100% proof loading was done correctly. > > On 10 April 2012 13:10, Ryan Smith <[email protected]> wrote: > > > Possibly try using the absolute path to your log4j.properties file for > > testing, just to be sure. > > > > > > > PropertyConfigurator.configure("/your/root/path/src/logging/log4j.properties"); > > > > > > >
