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 2006/03/16 07:07:20 UTC

DO NOT REPLY [Bug 38137] - Monitor deadlock in AsyncAppender

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=38137>.
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=38137


carnold@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED




------- Additional Comments From carnold@apache.org  2006-03-16 06:07 -------
I would appreciate if you could check if new AsyncAppender implementation (see
bug 38982) resolves the issues observed.  See first patch file for instructions
on modifying a log4j 1.2 build to use the new AsyncAppender.  Any critique or
comments would be appreciated, particularly if you would recommend incorporating
the new AsyncAppender in a log4j 1.2 bug fix release or developing a more
incremental modification.


-- 
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