for further questions about abbreviations
go to: http://members.aol.com/nigthomas/source.html
-Ursprüngliche Nachricht-
Von: Thilo Schottelius [mailto:[EMAIL PROTECTED]]
Gesendet: Donnerstag, 21. Juni 2001 09:01
An: 'LOG4J Users Mailing List'
Betreff: RE: Logging to multiple files from ap
Thilo,
Sure. PITA is the abbreviation of "Pain in the ass". Ceki
At 09:01 21.06.2001 +0200, you wrote:
>Dear Ceki,
>can you explain the abreviation "PITA" to a non native english speaking
>person?
>Thanks Thilo
>
>-Original Message-
>From: Ceki Gülcü [mailto:[EMAIL PROTECTED]]
>Sent: D
Dear Ceki,
can you explain the abreviation "PITA" to a non native english speaking
person?
Thanks Thilo
-Original Message-
From: Ceki Gülcü [mailto:[EMAIL PROTECTED]]
Sent: Donnerstag, 21. Juni 2001 06:28
To: LOG4J Users Mailing List
Subject: Re: Logging to multiple files from application
Just a note; many of the files in src/java/org/apache/log4j/xml/examples
use FileAppender instead of the new ConsoleAppender:
..
--Jeff
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
Hi Scott,
Thanks for taking the time to answer Reddy. I hate to be a PITA, but when
you say "it does not inherit from its parent (in this case root category)" you
probably mean
"it does not inherit appenders from its *ancestors* (e.g. the root category)."
Best regards, Ceki
At 11:39 21.06.20
Correct me if I am wrong,
I believe all categories inherit from the root category. The output of a log
statement of category C will go to all the appenders in C and its parents.
So, in your case since your maillog inherits from root category which routes
to weblogic log, they go to both the out
You need to use the line:
log4j.additivity.com.foo.mailagent.MailAgent=false
This means that it does not inherit from its parent (in this case root category).
Cheers,
Scott
>>> [EMAIL PROTECTED] 06/21/01 01:44am >>>
Hi,
We are running Weblogic server 5.1. We have an application log file whichc
Hi all,
I wrote some classes to override Category, CategoryFactory etc. It looks
almost identical to classes we have in examples/appserver.
However I am stuck because of PropertyConfigurator. It seems like I have to
create/initialize categories in the code, otherwise if I let
PropertyConfigurato
I am a first-time log4j user. I have setup a script to run the
SimpleSocketServer class and have defined the SocketAppender options for my
client application in a properties file. The client application is logging data
to the log server just fine. However, when the client application ends, I get a
Hello Ceki,
Do you mean that I specify specific appenders
and layouts in my main config file for for
the category "MY_APP" and then that I use
Category.getInstance("MY_APP")?
How does this work if I would like to have
different configuration files, one for the
main logging facility and other
Are you using a custom Priority class? Is there a mismatch between the client and the
server log4j versions? Ceki
At 18:27 20.06.2001 +0200, you wrote:
>Hello,
>
>I am trying to log statements coming from EJBs to a SocketServer.
>
>The logging to the SocketServer works fine usually, but when I
You'll be fine. You're giving up some of the nicer features of Log4j, of
course, but you're safe for threads and the like.
-Jim Moore
-Original Message-
From: Jamie Tsao [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 19, 2001 3:45 PM
To: [EMAIL PROTECTED]
Subject: RE: Using only the roo
Why don't use the category hierarchy? Ceki
At 12:30 20.06.2001 -0400, you wrote:
>Hello,
>
>I currently use PropertyConfigurator.configure(filename)
>to initialize the generic logging framework that is used
>throughout my applications. I would like to have a
>separate logging configuration fo
Hello,
I currently use PropertyConfigurator.configure(filename)
to initialize the generic logging framework that is used
throughout my applications. I would like to have a
separate logging configuration for a particular part of
my system (log to a different kind of appender, with a
different
Hello,
I am trying to log statements coming from EJBs to a SocketServer.
The logging to the SocketServer works fine usually, but when I try to log
from an EJB, I get no log, but this message on the SocketServer :
(this happens even after a basic log statement, such as : cat.debug("log me
please
Hi,
We are running Weblogic server 5.1. We have an application log file which
captures pretty much all the messages. I would like to have a separate log
file for our MailAgent. I added a fileAppender just for that class. For some
reason LOG4J is logging all the mail messages both into our appl
In your properties file (or XML config file) you will want to create two
appenders (FileAppender, since you want to log to a file) say XxxFile and
ZzzFile.
You will then attach each appender to a category, typically categories
equate with packages.
Example:
log4j.appender.XxxFile=org.apache.lo
Dear Norman,
1) create the categories:
category cat1=getInstance("aaa.bbb.xxx");
category cat2=getInstance("aaa.bbb.zzz");
2) assign the appenders to the categories:
cat1.addAppender(new FileAppender(new Layout(),"C:\file1");
cat2.addAppender(new FileAppender(new Layout(),"C:\file2");
You may a
Hello.
I'm kind of new to log4j, so my question could be newbie-like, sorry.
I want to be able to define explicitly that logging should be done only if
it occurs in a certain package.
For example:
A package "aaa.bbb" is devided into packages "aaa.bbb.xxx" and
"aaa.bbb.zzz".
Now i'd like to pu
John,
I agree with your sentiments.
I'm using Log4j and find that colleagues are having the same problems as
many people on the mailing list, namely:
- not understanding that NDC method calls set up a stack of information per
thread.
- some specific problems are easily solved with post-processi
20 matches
Mail list logo
