warnings from log4j -- where to look to resolve?

Hi, Each time I run a job, I get thousands of these warnings. I've looked at conf/log4j.properties and nothing out of the ordinary (a diff with the default log4j.properties shows no lines of consequence changed). Has anyone else come across this problem? Where else would I look to find potentiall

Re: warnings from log4j -- where to look to resolve?

Hi, Does your code instantiate and work with a self logger object? If so, is it a log4j instance or a commons logging one? On Mon, Jan 28, 2013 at 4:06 PM, Calvin wrote: > Hi, > > Each time I run a job, I get thousands of these warnings. I've looked at > conf/log4j.properties and nothing out of

Re: warnings from log4j -- where to look to resolve?

Hi Harsh, No self logger object is being used. On Mon, Jan 28, 2013 at 8:21 AM, Harsh J wrote: > > Hi, > > Does your code instantiate and work with a self logger object? If so, > is it a log4j instance or a commons logging one? > > On Mon, Jan 28, 2013 at 4:06 PM, Calvin wrote: > > Hi, > > > >

Re: warnings from log4j -- where to look to resolve?

Try passing -Dlog4j.debug via mapred.child.java.opts. That will clearly show you the problem as part of logs itself. Are these errors appearing in stdout/stderr or syslog? +Vinod Kumar Vavilapalli Hortonworks Inc. http://hortonworks.com/ On Jan 28, 2013, at 2:36 AM, Calvin wrote: > Hi, > > E