hadoop-mapreduce-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Calvin <iphcal...@gmail.com>
Subject Re: warnings from log4j -- where to look to resolve?
Date Mon, 28 Jan 2013 18:28:10 GMT
Hi Harsh,

No self logger object is being used.

On Mon, Jan 28, 2013 at 8:21 AM, Harsh J <harsh@cloudera.com> 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 <iphcalvin@gmail.com> 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 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
> > potentially conflicting settings for log4j?
> >
> > Thanks.
> >
> > ---
> >
> > attempt_201301161411_0244_m_000054_0: log4j:WARN Not allowed to write to a
> > closed appender.
> > attempt_201301161411_0244_m_000054_0: log4j:WARN Not allowed to write to a
> > closed appender.
> > attempt_201301161411_0244_m_000054_0: log4j:WARN Not allowed to write to a
> > closed appender.
>
>
>
> --
> Harsh J

Mime
View raw message