DO NOT REPLY [Bug 37768] - BasicConfigurator - duplicated output

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

DO NOT REPLY [Bug 37768] - BasicConfigurator - duplicated output

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

DO NOT REPLY [Bug 37768] New: - BasicConfigurator - duplicated output

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

DO NOT REPLY [Bug 37762] New: - RSSAppender

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

DO NOT REPLY [Bug 37756] - Chainsaw receives string index out of range error when using sockethubreceiver

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

DO NOT REPLY [Bug 37762] - RSSAppender

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

DO NOT REPLY [Bug 37756] - Chainsaw receives string index out of range error when using sockethubreceiver

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

svn commit: r351860 - /logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/layout/EventDetailLayout.java

Author: psmith Date: Fri Dec 2 16:41:09 2005 New Revision: 351860 URL: http://svn.apache.org/viewcvs?rev=351860&view=rev Log: Bug 37756 A thread-safety issue with the layout being used. Rather than add a sync block to the layout class itself, I have placed a sync block here instead, which I beli

svn commit: r351831 - /logging/sandbox/log4j/contribs/

Author: carnold Date: Fri Dec 2 12:27:42 2005 New Revision: 351831 URL: http://svn.apache.org/viewcvs?rev=351831&view=rev Log: Move log4j/contribs to sandbox Added: logging/sandbox/log4j/contribs/ - To unsubscribe, e-mail:

svn commit: r351832 - /logging/sandbox/log4j/contribs/trunk/

Author: carnold Date: Fri Dec 2 12:27:54 2005 New Revision: 351832 URL: http://svn.apache.org/viewcvs?rev=351832&view=rev Log: Move log4j/contribs to sandbox Added: logging/sandbox/log4j/contribs/trunk/ - copied from r351831, logging/log4j/trunk/contribs/

Re: Log4j 1.3 Woes

On Fri, 2005-12-02 at 09:32 -0800, Mark Womack wrote: > So, I don't remember if anything specific has already been applied to > 1.3 for the deadlock issue (Elias can speak to that better probably). Nothing in particular was applied. (I don't have commit access to apply changes either to effectu

Re: Log4j 1.3 Woes

Mark Womack wrote: So, I don't remember if anything specific has already been applied to 1.3 for the deadlock issue (Elias can speak to that better probably). However, it is an issue that will be addressed in 1.3 in the near future. We've been very reluctant to make any of these kinds of chan

Re: Log4j 1.3 Woes

On 11/29/05, Jess Holle <[EMAIL PROTECTED]> wrote: > I appreciate the forthright responses from you, Curt, and others. No reason for anything else from anyone here. We all want to do the right thing. > I apologize for getting a bit hot on these issues. It would be good if > the 1.3 documentati

[RESULT][VOTE] Release of log4j 1.2.13

This proposal has been accepted by the log4j committers, with positive votes from the community at large.  I will do the official tagging and building this Saturday (I'll be sure to tag the site as well). -Mark

DO NOT REPLY [Bug 37756] New: - Chainsaw receives string index out of range error when using sockethubreceiver

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 and Java 5

On Fri, 2 Dec 2005, Endre Stølsvik wrote: | | One more thing about concurrent.jar: if the inclusion of a entirely new | library dependency sounds bad (which I personally think!), one have the | option of just "stealing" the parts that are necessary: the magic is not | in new JVM features, but

Re: Log4j and Java 5

On Fri, 2 Dec 2005, Yoav Shapira wrote: | (for example, on the Tomcat mailing lists, we've seen far more JSE5 than | JDK 1.4 queries not just recently, but for almost two years now), Do remember that the user base (hopefully!) also is _expanding_, and that _new_ users (and instances?) probably

Re: Log4j and Java 5

Yoav Shapira wrote: Hi, Doug Lea's concurrent library is a good piece of software. We used it at my old workplace for a couple of years in heavy apps, never a problem. And now it's part of JSE 5 so future migration will be easy. One could also imagine a simple class that detects if running on

Re: Log4j and Java 5

Hi, Doug Lea's concurrent library is a good piece of software. We used it at my old workplace for a couple of years in heavy apps, never a problem. And now it's part of JSE 5 so future migration will be easy. One could also imagine a simple class that detects if running on JSE5 and later and the

Re: Log4j and Java 5

On Thu, 1 Dec 2005, Jess Holle wrote: | Has anyone tried replacing the synchronization in log4j with Java 5 locks to | and done any benchmarks? | | I'm curious as I think it would be interesting to have a lock factory which | produces something like the existing locks for pre-Java-5 JVMs and Java