Re: Log4J Ignores log4j.LogLevel

From:

"Kevin Sandal" <noone@nowhere.biz>

Newsgroups:

comp.lang.java.help

Date:

Thu, 26 Jul 2007 19:57:25 GMT

Message-ID:

<JLsy3q.K62@news.boeing.com>

Going to rename my own log class to XYZLogger (or some such).

Basically, each class that is going to use the logging facility will call my
Singleton XYZLogger. On the first invocation, a customized properties file
(config\log4j.properties) will be read in. Then the other classes will use
it like "XYZLogger.getInstance( CallingClass.getClass() )".

This all works. Except the level of logging. It is always set at "DEBUG"
even if I choose "INFO" in the properties file.

Thanks Mark & Lew for taking the time to look at this.

Kevin

"Lew" <lew@lewscanon.nospam> wrote in message
news:DtqdnUFQWvETzTrbnZ2dnUVZ_sPinZ2d@comcast.com...

Mark Space wrote:

Lew wrote:

private static Log _apacheLog = null;

{

        if( null == _myLogger )
        {
            _myLogger = new Logger();
        }

}

return _myLogger;

From this we see that _myLogger will change every time the factory
method is invoked. Why do you store the value in the static member and
return it, both?

Well, the _myLogger variable is private, so how else would it be
accessed? Looks like a Singleton pattern to me. _myLogger shouldn't
change with each invocation; it's only assigned when _myLogger is null to
begin with, unless I'm missing something.

You are right, I missed that. Of course, log4j will always deliver the
same Logger if you pass the same Class or String to the Logger factory
anyway, so I'm questioning again why the need to provide a custom factory
class.

The configuration of the Logger would be much easier to understand (for
me, at least) if the Logger in question were log4j's. So I reiterate my
suggestion that the OP use the log4j Logger class and its factory method.

--
Lew