In the paragraph beginning 'Loggers may be assigned levels.', it goes on to
say 'Although we do not encourage you to do so, you may define your own
levels by sub-classing the Level class. A perhaps better approach will be
explained later on.' I have checked out the examples in the 1.2.8 src
Hello!
I'm getting the log4j error message
log4j:WARN No appenders could be found for logger (SomeClass).
log4j:WARN Please initialize the log4j system properly.
This happens in a test case, which has the following main function:
import junit.framework.TestSuite;
public class SomeTestSuite
Here you go. It's pretty straightforward. Lemme know if you have any
questions.
-Original Message-
From: Tom Eugelink [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 11, 2003 21:50
To: Log4J Users List
Subject: Re: automatic reload
I also use a servlet to reload, but since I've gotte
OK, you are forcing me to admit my sins. This morning I woke up and guessed
the problem (I knew I should have waited another day before asking for
help). I had to get to work to verify I was right. Mark was sort-a on the
right track except I was the culprit.
As Paul and Mark pointed out, everyt
On Thu, 2003-11-13 at 03:45, Scott Smith wrote:
> OK, you are forcing me to admit my sins. This morning I woke up and guessed
> the problem (I knew I should have waited another day before asking for
> help).
I think that there must be a universal Law somewhere about this, I've
also found numero
On Thu, 2003-11-13 at 02:22, Dimitri Pissarenko wrote:
> Hello!
>
> I'm getting the log4j error message
>
>
> log4j:WARN No appenders could be found for logger (SomeClass).
> log4j:WARN Please initialize the log4j system properly.
>
>
>
Most likely candidate is that some where in the Test c
I was also thinking that you might consider putting a Log message
immediately following the BasicConfigurator.configure() call. If you
receive this message to the console, then something else is re-initing
Log4j.
BTW, 2 things about your code:
* The BasicConfigurator will automatically add and c
Hi all-- (I'm a new user, so please forgive).
Here's my simple program:
--
import org.apache.log4j.*;
public class MyApp
{
static Logger logger = Logger.getLogger("myapp");
public static void main (String[] args)
The BasicConfigurator already creates and configures a ConsoleAppender
automatically, so the other one that you are adding is doubling up. (The
output with the time is your appender is your one I think).
cheers,
Paul
On Thu, 2003-11-13 at 09:40, Chang, Betty wrote:
> Hi all-- (I'm a new user, s
Paul -
Are you sure about that? I thought that only happened with
BasicConfigurator.configure() (no params).
/**
Add appender to the root category.
@param appender The appender to add to the root category.
*/
static
public
void configure(Appender appender) {
Logger root =
Hi -- I removed my ConsoleAppender, and just call BasicConfigurator()
with no parameters, and I STILL get that extra line.
Here's the code:
import org.apache.log4j.*;
public class MyApp
{
static Logger logger = Logger.getLogger("myapp");
public static void main (String[] args)
Hi -- If I'm picking up some kind of default config file, what would
it be called?
Thanks
Betty
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 12, 2003 3:01 PM
To: [EMAIL PROTECTED]
Subject: RE: I cannot figure out where my extra messag
On Thu, 2003-11-13 at 10:00, [EMAIL PROTECTED] wrote:
> Paul -
>
> Are you sure about that? I thought that only happened with
> BasicConfigurator.configure() (no params).
>
> /**
> Add appender to the root category.
> @param appender The appender to add to the root category.
> */
>
log4j.properties or log4j.xml, somewhere in the classpath.
Paul
On Thu, 2003-11-13 at 10:10, Chang, Betty wrote:
> Hi -- If I'm picking up some kind of default config file, what would
> it be called?
>
> Thanks
>
> Betty
>
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[E
I haven't programmatically configured Log4J as you are doing here, but
if you were doing this using the log4j.properties file I would say you
are getting output from the root logger as well as your own logger for
'myapp'.
Try setting up a log4j.properties file and don't add the console
appender to
Hi -- Thanks for all your help! The -Dlog4j.debug did the trick. It
was picking a log4j.properties from within the axis.jar file. Just
doing a "dir /s" did not find one since it was within the jar file.
Okay -- so my next question is -- what's the easiest way to get my
program to ignore that
> Okay -- so my next question is -- what's the easiest way to get my
> program to ignore that log4j.properties file? (I don't really want
> to use my own file -- I just want to configure it in the code).
I think the following System property would do it:
-Dlog4j.defaultInitOverride=true
Thi
I am using jboss-3.0.8_tomcat-4.1.24(with log4j default) + velocity1.3.1
I found there are a lot of STDERR messages in my Jboss console when
the tomcat load Velocity templates (templates is running and can be
seen from the broswer).
21:04:24,741 ERROR [STDERR] log4j:ERROR Attempte
18 matches
Mail list logo
