cvs commit: logging-log4j/src/java/org/apache/log4j/spi RepositorySelector.java

hoju2004/12/03 23:47:05 Modified:src/java/org/apache/log4j Hierarchy.java src/java/org/apache/log4j/spi RepositorySelector.java Log: Fix typos... repostiroy ---> repository Revision ChangesPath 1.58 +2 -2 logging-log4j/src/java/org/apache/log4

Re: Joran, RollingFileAppender, and Rollover failure warnings

At 02:03 PM 12/3/2004 +0100, you wrote: > >Jake, > >I've looked into the examples you've sent me. Can't make anything out >of them. > I added stacktrace output to RollingFileAppender.rollover() to debug this issue. Here's the relevant part... DEBUG[Thread-1]: pache.log4j.rolling.RollingFileAppen

Re: Log4j-1.3 autoconfiguration default?

At 03:24 AM 12/4/2004 +, you wrote: >Hi Ceki, > I'm having several interesting problems >trying to build and run the log4j unit tests at the moment >on my system which I suspect are due to my environment not >being quite right yet after a recent clean OS re-install >:-( > Can you explain your i

DO NOT REPLY [Bug 32527] - log4j initialization in java1.3 no dom in class path.

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

Re: Log4j-1.3 autoconfiguration default?

Hi Ceki, On Fri, 03 Dec 2004 13:49:39 +0100 Ceki Gülcü <[EMAIL PROTECTED]> wrote: Hello Andy, Thank you for taking the time to express your concerns. I appreciate it. While I agree with most of your comments, it think it is important to put them in relation with the facts. 1) The NPE problem ca

DO NOT REPLY [Bug 32527] New: - log4j initialization in java1.3 no dom in class path.

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

Re: Joran, RollingFileAppender, and Rollover failure warnings

On Dec 3, 2004, at 7:03 AM, Ceki Gülcü wrote: One of the important tasks to be done before releasing 1.3, is to write unit tests which go through the whole web-app lifecycle to check that log4j releases all resources correctly. I started doing that with jetty but got sidetracked. Anyway, I'd apprec

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

ceki2004/12/03 09:17:35 Modified:src/java/org/apache/log4j/helpers IntializationUtil.java src/java/org/apache/log4j Hierarchy.java Log: Added LogLog statements showing information about Logger creation, and LoggerRepository configuraiton. Revision Changes

Re: Joran, RollingFileAppender, and Rollover failure warnings

Jake, One point where log4j 1.3alpha3 will silently fail is if your XML config file contains a reference to log4j.dtd in the DOCTYPE declaration. But you don't have that as your log4j.xml file attests: FYI, Joran currently takes to passes at config files. Once to verify that its well-for

cvs commit: logging-log4j build.xml

ceki2004/12/03 06:38:10 Modified:.build.xml Log: after alpha-3, alpha-4 Revision ChangesPath 1.121 +1 -1 logging-log4j/build.xml Index: build.xml === RCS file: /home/cvs/logging-

Re: Joran, RollingFileAppender, and Rollover failure warnings

Jake, I've looked into the examples you've sent me. Can't make anything out of them. One of the important tasks to be done before releasing 1.3, is to write unit tests which go through the whole web-app lifecycle to check that log4j releases all resources correctly. I started doing that with jetty

Re: Log4j-1.3 autoconfiguration default?

Hello Andy, Thank you for taking the time to express your concerns. I appreciate it. While I agree with most of your comments, it think it is important to put them in relation with the facts. 1) The NPE problem cannot be triggered from configuration files but only by java code actively trying to se

Re: Log4j-1.3 autoconfiguration default?

At 09:42 PM 12/2/2004, Paul Smith wrote: Any reason why? NPE's are not useful to the end user. A bait? I'll take it. Saying that no one has use for NPEs is like saying no one has use for hemorrhoids. For the time being, only Jake encountered this particular NPE issue. He did so because of his very