Hi Tomasz,
Typically logging issues wind up having little or nothing to do with the actual
code being used to do the logging.
Where you need to be looking is classpath and jar issues, which requires
project context, not source code.
I did a quick google search on "netbeans log4j commons logging" and found a few
interesting hits. One suggestion was to add:
System.out.println(getClass().getClassloader().getResource("log4j.properties"));
to figure out exactly which log4j.properties file is being used.
And yes, problems with logging frameworks are frustrating. I've spent many
hours tracking down issues, especially in the land of app servers (Jetty,
Resin, Tomcat, etc).
But since everyone on this list is trying to help for free, a less antagonistic
tone would be appreciated.
Regards,
-- Ken
On Apr 10, 2012, at 10:20am, tommmmmm wrote:
> On 10 April 2012 18:57, Ryan Smith <[email protected]> wrote:
>
>> Possibly try using a log4j.xml file instead of a log4j.properties file.
>> Ive seen this fix a similar problem I had a while back. Its worth a shot
>> anyways, right?
>>
>
> No.
>
> + I read http://wiki.apache.org/logging-log4j/Log4jXmlFormat
> Tried getting even the simplest example to work - No appenders could be
> found for logger.
>
> So I prefer to stick with normal proprties.
>
> And it's not like I have an eternity to play with a logger... I have so
> many other so much more important things to code with a deadline long past.
>
> For the purpose of clarity. here is the code:
> http://pastebin.com/H1PWqdBc
>
> Question same as always: why doesn't it work?
--------------------------
Ken Krugler
http://www.scaleunlimited.com
custom big data solutions & training
Hadoop, Cascading, Mahout & Solr
