What version of commons-logging are you using? If you use Log4j for Tomcat
logging, put both log4j.jar and commons-logging.jar (not
commons-logging-api.jar) in common/lib and your log4j.xml or log4j.properties
in common/classes. And make sure you use commons-logging version 1.0.4 or
above.
Jake
Hi;
Well, I'm off for a fun weekend - thank you to all for helping.
If by any chance any of you are working this weekend...
As you said, what I want is:
warn from anything to stdout and tomcat
info from org.apache to stdout
thanks - dave
David Thielen
303-499-2544
www.windwardreports.com
---
Except he wants two different levels, he wants one level to go to blah, and
another level to go to blah.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of James Stauffer
Sent: Friday, September 23, 2005 3:26 PM
To: Log4J Users List
Subject: Re: Duplicate
On 9/23/05, David Thielen <[EMAIL PROTECTED]> wrote:
> Ok, I think I get it now. Is this correct:
>
> All and entries cause log entries to be written.
>
> It does not look for duplicates so having something in there twice cause it
> to be written twice to the same appender.
>
> A with additivity
Ok, I think I get it now. Is this correct:
All and entries cause log entries to be written.
It does not look for duplicates so having something in there twice cause it
to be written twice to the same appender.
A with additivity='true' means do this in addition to root for the
name= classes.
or .
It is just the root of the logger tree.
On 9/23/05, David Thielen <[EMAIL PROTECTED]> wrote:
> Hi;
>
> I think I don't understand and The way I read the docs
> is what is done to all classes for the appenders listed. The
> adds to that.
>
> So I put the following:
>
>
You could test it by quickly telling the logger to also print to stdout
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Thielen
Sent: Friday, September 23, 2005 1:02 PM
To: 'Log4J Users List'
Subject: RE: Duplicate log entries - 1 last issue
Ok, bu
Ok, but why does nothing get written to tomcat when I add the for
stdout? Shouldn't tomcat still get written to? It's like the says
ONLY write the classes listed to what it has, not also???
Thanks - dave
David Thielen
303-499-2544
www.windwardreports.com
-Original Message-
From: Schuw
The root section is called every time a logging section is received. Any
logging events where the logger name starts with org.apache causes that logging
section to be used IN ADDITION to the root section.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Hi;
I think I don't understand and The way I read the docs
is what is done to all classes for the appenders listed. The
adds to that.
So I put the following:
Which puts all warn and worse in those 2 appenders. And that work
AHHH - thank you
David Thielen
303-499-2544
www.windwardreports.com
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Michael A Chase
Sent: Friday, September 23, 2005 7:37 AM
To: log4j-user@logging.apache.org
Subject: Re: Files aren't rolling over
On Fri, 23 Sep 20
I think you will need to add something to your configuration to set '
org.apache.log4j' to WARN/ERROR. This is something we need to look into in
the drive to beta.
hth,
-Mark
On 9/23/05, [EMAIL PROTECTED] <
[EMAIL PROTECTED]> wrote:
>
> Hello!
>
> How can I turn off the logj4 logs ins Log4J 1.3 a
I think the answer is that they can only be turned off by changing the
code and that they will be removed at some time before it is released.
i.e. That is just part of it being an alpha release.
On 9/23/05, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> Hello!
>
> How can I turn off the logj4 log
Hello!
How can I turn off the logj4 logs ins Log4J 1.3 alpha 6?
They appear like this:
log4j:INFO Returning existing logger
[org.apache.log4j.joran.spi.Interpreter] in repository [default].
log4j:INFO Returning existing logger
[org.apache.log4j.joran.spi.Interpreter] in repository [default].
log
Hi all,
I have got a problem with log4j 1.3 alpha 6 and tomcat 5.5.9:
If I start the tomcat 5.5.9 I get the following exception:
log4j:INFO Creating new logger
[org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/kba]] in
repository [default].
log4j:INFO Creating new logger [org.apach
On Fri, 23 Sep 2005 07:22:32 -0600, David Thielen wrote:
> None of our files rolled over from yesterday. Any idea why?
You're using RollingFileAppender, it rolls when files hit a certain size,
100KB in your case, not when the date changes. Maybe you want
DailyRollingFileAppender instead.
>
What are the sizes of the files?
On 9/23/05, David Thielen <[EMAIL PROTECTED]> wrote:
> None of our files rolled over from yesterday. Any idea why?
>
> Thanks - dave
>
>
>
> http://jakarta.apache.org/log4j/";>
>
>
>
>
>
>
On 9/22/05, David Thielen <[EMAIL PROTECTED]> wrote:
> If I have:
>
>
>
>
> Then nothing is written to the tomcat appender.
Changing that to the following would also send the output to tomcat
> If I
None of our files rolled over from yesterday. Any idea why?
Thanks - dave
http://jakarta.apache.org/log4j/";>
19 matches
Mail list logo
