Hello,
I want to set the Threshold for one class to DEBUG. Is this possible when I
use the xml configuration file.
In a log4j.property file it is just adding the following line:
log4j.logger.classname=DEBUG
Thanks a lot
Dries
Hi,
Use the following:
category name=package.xxx.xxx.loggername
priority value=INFO /
/category
Regards,
Andreas Bothner
-Original Message-
From: De Moor Dries [mailto:[EMAIL PROTECTED]
Sent: Friday, 24 October 2003 12:18
To: '[EMAIL PROTECTED]'
Subject: Set Threshold for
Hi,
Sorry, these are the new element names:
logger name=package.xxx.xxx.loggername
level value=INFO /
/logger
Regards,
Andreas Bothner
-Original Message-
From: De Moor Dries [mailto:[EMAIL PROTECTED]
Sent: Friday, 24 October 2003 12:18
To: '[EMAIL PROTECTED]'
Subject: Set
Hi,
I saw in the 1.4 JDK that there were new classes introduced concerning logging, which
seems to be a base for Log4J. When I take a look at the class hierarchy of Log4J, it is
not a subclass of those JDK logging classes (I think the reason is that Log4J is older
than the 1.4 JDK...).
So, what
Howdy,
http://www.qos.ch/logging/thinkAgain.html
http://nagoya.apache.org/wiki/apachewiki.cgi?Log4JProjectPages/Log4jvsJDKLogging
http://builder.com.com/5100-22-1046694.html
Log4j will be around. The next major release, v1.3, is going to have several great
new features to further distance
Some people may disagree but we have take the approach of using the
commons-logging API.
We have configured it to use log4j we appropriate.
If needed I can configure commons-logging to use JDK 1.4 logging.
You will probably find JDK 1.4 logging support in log4j via an append or
someting else in
At 04:25 PM 10/24/2003 +0200, you wrote:
Some people may disagree but we have take the approach of using the
commons-logging API.
commons-logging has never been anything but a pain in the butt in every
case I've seen it used. The classloader issues are never-ending.
We have configured it to use
100% agreed. Log4j is better supported, and probably has an order of
magnitude more functionality - if not more. It's pretty much a no-brainer.
There's a book about Log4j that's excellent.
https://www.qos.ch/shop/products/clm_t.jsp
Log4j was a finalist in 2001 for the JavaWorld Editors
At 10:23 AM 10/24/2003 -0400, Shapira, Yoav wrote:
Howdy,
http://www.qos.ch/logging/thinkAgain.html
The above link is more related to commons-logging than to JDK 1.4 logging
per se.
http://nagoya.apache.org/wiki/apachewiki.cgi?Log4JProjectPages/Log4jvsJDKLogging
I modified and edited the above
Howdy,
http://nagoya.apache.org/wiki/apachewiki.cgi?Log4JProjectPages/Log4jvs
JDKL
ogging
I modified and edited the above page. Please let me know what you
think.
I took a look -- I like it ;) I corrected a couple of small text
errors. I would like to add a link to the phrase that says log4j
Let me, as a log4j user, give my 2 cents. I looked at the Java 1.4
logging classes and decided they were inferior to log4j. Since log4j is
an external JAR, it will not only be available in JDK1.4 but also in
1.5, ... and you can already use them in 1.3. So log4j is the way to go.
Tom
Matthias
Some people may disagree
Yup ;-)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Oh, and let me add another opinion to my own mail. I think that adding
more and more functionality to the JVM (what Sun is doing now) is not a
good thing. I prefer a lean mean core engine and addon JARs. Want SSL?
Add SSL.jar. Want logging? Add logging.jar. Want RDBMS? Add JDBC.jar.
I'd vote
great point. Hopefully someone at Sun is listening.
-Original Message-
From: Tom Eugelink [mailto:[EMAIL PROTECTED]
Sent: Friday, October 24, 2003 2:26 PM
To: Log4J Users List
Subject: Re: Log4J vs. java.util.logging
Oh, and let me add another opinion to my own mail. I think that
Isn't that what JCP is for?
;-)
-Marc
-Original Message-
From: Lutz Michael [mailto:[EMAIL PROTECTED]
Sent: Friday, October 24, 2003 2:55 PM
To: 'Log4J Users List'
Subject: RE: Log4J vs. java.util.logging
great point. Hopefully someone at Sun is listening.
-Original
You use the product that has superior functionality and
works for you now. Why would anybody choose an inferior
library and then have to waste resources to enhance it
just because it MAY become the standard in the future.
What if Sun doesn't enhance it anymore, or what if they
do and you have
http://nagoya.apache.org/wiki/apachewiki.cgi?Log4JProjectPage
s/Log4jvsJDKLogging
I modified and edited the above page. Please let me know what
you think.
Much better. Thanks!
The biggest reasons to use log4j, in my mind, are:
1) It is opensource, so if you need to make changes or add
I just came across a deadlock condition in my code brought out by
Log4J. Here is a simplified view of the objects in play:
class State {
Logger log1;
synchronized void setState() {
// Something takes a long time here
log.debug(hello world);
}
synchronized Object
On Fri, 2003-10-24 at 14:17, Elias Ross wrote:
[cut]
So, I am wondering why can't the rendered render without holding the
lock on 'org.apache.log4j.spi.RootCategory'?
I'm replying to myself, I know...
Another work-around for this sort of deadlock would be for me write,
instead of
Okay, let me finish, I'm sorry I hit send early by mistake. :-)
On Fri, 2003-10-24 at 15:26, Elias Ross wrote:
Here is the stack trace:
org.apache.log4j.WriterAppender.append(WriterAppender.java:150)
org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:221)
- locked
Hi,
I had sent this to the Tomcat list, but it seems to be more of a jog4j
issue. So trying my luck here :)
Can anyone shed some light as to why I get the following error when I try
to access the JSP..
javax.servlet.ServletException: org/apache/log4j/Category at
21 matches
Mail list logo
