How about using a text processor to filter the log output?
How about writing log entries to a database (as well as to a flat file) and
querying the database where thread id = ? With both of these solutions,
there's no code to write.
-Original Message-
From: Samya Ghosh [mailto:[EMAIL PROT
It's probably counter-productive, but I just have to chime in here.
I too have been highly entertained by this exchange.
My compliments to those who manage to respond in a level-headed fashion!
-Original Message-
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 04
I would hazard a guess that you haven't read much of the material available
on how to use log4j. Loggers inherit their behavior from a runtime hierarchy
based on their names. java.util is the parent of java.util.foo and java.util
is an ancestor of java.util.foo.bar where those dot separated names
It means that the root logger's level is set to DEBUG (which basically means
that all logging requests will produce output) and the A1 appender is being
placed into its appender set. The A1 appender is defined in the next
statement in the configuration properties file.
Does that help?
-Origin
