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

           Summary: Add non-blocking option for AsyncAppender.
           Product: Log4j
           Version: 1.3alpha
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Appender
        AssignedTo: log4j-dev@logging.apache.org
        ReportedBy: [EMAIL PROTECTED]


As discussed in log4j-dev message "Contribution of non-blocking socket appender"
on 2006-01-11 (http://marc.theaimsgroup.com/?t=113700495300004&r=1&w=2), it
would be desirable to configure AsyncAppender so that logging requests made when
the buffer is full do not cause the requesting thread to block.

This feature is included in a resubstantial rewriting of AsyncAppender that will
follow which hopefully addresses the large number of deadlock reports with the
current AsyncAppender.

A new configuration "blocking" with a default value of true is added.  If set to
false, log requests received while the buffer is blocked will be used to update
a Map that is used to maintain the highest severity and count of messages for
each encountered logger.  After the messages in the buffer are output, the map
will be used to generate messages like:

org.example.foobar ERROR Discarded 15 messages due to full event buffer
including: Message from first ERROR on org.example.foobar

-- 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to