DO NOT REPLY [Bug 28647] - Add "Flush on Level" capability to FileAppender

[bu...@apache.org]

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


odupuy@bigfoot.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P5




------- Additional Comments From odupuy@bigfoot.com  2006-08-23 13:40 -------
Hi all,

I totally aggree with the flushing being tied to the level of the event. This 
totally makes sense and would be good to have it in the default log4J.

As Simon, I also use a shutdown hook in my application to address the issue - 
i.e. automatically flush on VM exit.

The only way I found to flush was to close all the appenders. This is fine as I 
am stopping the application but a way to flush globally all the logs without 
closing the appenders in a very simple way should also be there.
Let's imagine I want to flush all the logs using some admin interface to 
examine them but I don't want to close them even to reopen seconds later (to 
not loose events and getting error messages everywhere while they are created). 
What are my options in this case????
So flushing should be present in each appender that could delegate to sub 
appenders if required.

Olivier DUPUY

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