You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2005/03/04 22:37:25 UTC
DO NOT REPLY [Bug 33855] -
Log4j should supply concurrent (and deadlock-free) appender classes
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=33855>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=33855
------- Additional Comments From eross@m-qube.com 2005-03-04 22:37 -------
Created an attachment (id=14405)
--> (http://issues.apache.org/bugzilla/attachment.cgi?id=14405&action=view)
Diffs against March 4th codebase
* Make PatternLayout thread-safe and about 2-3 times more efficient. (Writer
is slower than StringBuffer.)
* src/java/org/apache/log4j/spi/ThrowableInformation.java
If you want throwable information available, the Throwable class should
output the stack trace properly using printStackTrace. Under JDK 1.4, this
class is very inefficient and largely unneccessary. Perhaps make it an System
property to turn on?
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org