RE: cvs commit: logging-log4j/tests/src/java/org/apache/log4j LoggerTestCase.java StressCategory.java

Re: New TRACE Level Kudos to you Yoav, I was trying to get myself mentally ready to have a crack at doing this myself. Thankfully I never started it! Very much appreciated. Cheers, Paul Smith - To unsubscribe, e-mail: [EMAIL PR

RE: cvs commit: logging-log4j/tests/src/java/org/apache/log4j LoggerTestCase.java

At 09:49 PM 8/5/2004, you wrote: Yeah, I noticed it's just tests. It was a surprise and a marginal annoyance, but no big deal. I hope the web-app reloading tests are not dependant on jetty-specific behavior, but then again any testing is better than none. Exactly. The tests are done using jetty s

RE: cvs commit: logging-log4j/tests/src/java/org/apache/log4j LoggerTestCase.java

Hola, >> Undid the removal of PassByJNDI.java from the tests/build.xml >> compilation. I committed that by accident before. I still don't like >> needing Jetty to build, though. > >Jetty is needed for building the tests, not log4j itself. Using jetty we >can test log4j in relation to web-app

Re: cvs commit: logging-log4j/tests/src/java/org/apache/log4j LoggerTestCase.java

At 09:25 PM 8/5/2004, you wrote: yoavs 2004/08/05 12:25:51 Modified:src/java/org/apache/log4j Category.java PropertyConfigurator.java src/java/org/apache/log4j/jmx LoggerDynamicMBean.java src/java/org/apache/log4j/lf5/viewer/category

DO NOT REPLY [Bug 27371] - java.lang.ThreadDeath caused by log4j when reloading Tomcat app

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

cvs commit: logging-log4j/tests/src/java/org/apache/log4j LoggerTestCase.java

yoavs 2004/08/05 12:25:51 Modified:src/java/org/apache/log4j Category.java PropertyConfigurator.java src/java/org/apache/log4j/jmx LoggerDynamicMBean.java src/java/org/apache/log4j/lf5/viewer/categoryexplorer

RE: Levels in UGLI

Hola, OK, I understand, and it makes sense. Thanks, Yoav Shapira Millennium Research Informatics >-Original Message- >From: Ceki Gülcü [mailto:[EMAIL PROTECTED] >Sent: Thursday, August 05, 2004 2:12 PM >To: Log4J Developers List >Subject: Re: Levels in UGLI > >At 07:51 PM 8/5/2004, you

Re: Levels in UGLI

At 07:51 PM 8/5/2004, you wrote: Hi, Which levels should be defined in org.apache.ugli.Logger? I see debug, info, warn, error, but no off, all, fatal, or trace. off and all are not printing methods. No one ever writes nor would want to write: logger.off("some msg"); (a never printing message)

Re: cvs commit: logging-log4j/tests/src/java/org/apache/log4j LoggerTestCase.java StressCategory.java

Hi Yoav, A few comments about your commit. First, the new trace methods should be added to Logger and not Category. Remember that log4j will always produce Logger instances and never pure Category instances. Second, the commit message contains massive amount of changes due probably to white spa

Levels in UGLI

Hi, Which levels should be defined in org.apache.ugli.Logger? I see debug, info, warn, error, but no off, all, fatal, or trace. I'm fine with that, but I'm just curious as to the reasoning that went into choosing the UGLI levels. Yoav Shapira Millennium Research Informatics This e-mail, in

cvs commit: logging-log4j/tests/src/java/org/apache/log4j LoggerTestCase.java StressCategory.java

yoavs 2004/08/05 10:45:46 Modified:src/java/org/apache/log4j Category.java Level.java Logger.java testsbuild.xml tests/src/java/org/apache/log4j LoggerTestCase.java StressCategory.java Log: Added TRAC

Re: Adding TRACE to CVS?

Yoav, Even if I think adding the TRACE level will lead to future complications, we had a binding vote on the subject. The results were in favor of adding the TRACE level. So, please go ahead. And thanks for looking into this... At 03:21 PM 8/5/2004, you wrote: Hi, Would anyone object if I go ahe

DO NOT REPLY [Bug 27371] - java.lang.ThreadDeath caused by log4j when reloading Tomcat app

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

FW: log4j SEVERE ThreadDeath in Tomcat 5.0.25

Hola, I'm forwarding this to commons-dev to include the commons-logging developers on this discussion. What do you guys think? Is there another readily available key to use when caching LogFactory objects? Or perhaps a way for commons-logging to not cache these, or maybe discard the cache wh

DO NOT REPLY [Bug 27371] - java.lang.ThreadDeath caused by log4j when reloading Tomcat app

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu