I am replyign to an older post... so I hope in comes in the correct
thread..."Re: shut off internal logger output" (see below)
I found a way by myself but is currently not so satisfying. If someone
has another solution i.e. by using the configuration please let me
know.
Have a l
Actually I would be happy if I could keep my chainsaw client appender(and
the ability to connect using the socket receiver or not)
and get rid of the log4j:INFO message stating the socket is trying to
connect. I know if I comment out the chainsaw appender in the config file it
goes away but I'm
On Jun 28, 2005, at 7:18 PM, Dave wrote:
I tried
I'm using 1.3.0alpha6 in WSAD
This gets rid of the statements below generated internally starting
with
DEBUG
I need to get rid of the log4j:INFO stuff
is there any way?
I was working on this yesterday to get the log4j 1.2 tests passin
At 01:18 AM 6/29/2005 +0100, you wrote:
>I tried
>
>
>
>
>I'm using 1.3.0alpha6 in WSAD
>
>This gets rid of the statements below generated internally starting with
>DEBUG
>I need to get rid of the log4j:INFO stuff
>
>is there any way?
>
Build from source. alpha6 is seriously old at this point.
I tried
I'm using 1.3.0alpha6 in WSAD
This gets rid of the statements below generated internally starting with
DEBUG
I need to get rid of the log4j:INFO stuff
is there any way?
** configurationOptionStr=null
** End of LogManager static initializer
log4j:INFO Creating new logger [com.raythe
