You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4net-dev@logging.apache.org by "Nicko Cadell (JIRA)" <ji...@apache.org> on 2005/08/30 00:34:04 UTC

[jira] Resolved: (LOG4NET-11) Add Flush command to API

     [ http://issues.apache.org/jira/browse/LOG4NET-11?page=all ]
     
Nicko Cadell resolved LOG4NET-11:
---------------------------------

    Fix Version: 1.2.10
     Resolution: Fixed
      Assign To: Nicko Cadell

Added Flush(true) method to BufferingAppenderSkeleton. This method forces the current buffer to be flushed to the output even if the appender is in lossy mode.

To find the appender use the LogManager.GetRepository().GetAppenders() method, then for each BufferingAppenderSkeleton call Flush(true).

> Add Flush command to API
> ------------------------
>
>          Key: LOG4NET-11
>          URL: http://issues.apache.org/jira/browse/LOG4NET-11
>      Project: Log4net
>         Type: New Feature
>   Components: Core
>     Versions: 1.2.9
>  Environment: From sourceforege - 764025 - Kevin Conroy - kmconroy
>     Reporter: Nicko Cadell
>     Assignee: Nicko Cadell
>      Fix For: 1.2.10

>
> While using Buffering is a wonderful way to help improve
> performance, I would like the ability to programatically
> tell the current ILog object to flush any buffers that
> exist on the appenders that I've been logging to so that
> I can get any messages that I've sent rather than
> waiting for the buffer to fill up.
> Thus, one might be able to do the following:
> "log.Flush();"
> and then any messages sent to that ILog object would
> be processed.
> Kevin Conroy - kmconroy
> ----
> I vote for this one too!
> dcazzulino

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira