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 2004/05/28 14:14:51 UTC
DO NOT REPLY [Bug 18965] -
DailyRollingFileAppender leaves file locked causing roll to fail and logging to be discarded!
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=18965>.
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=18965
DailyRollingFileAppender leaves file locked causing roll to fail and logging to be discarded!
ceki@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
------- Additional Comments From ceki@apache.org 2004-05-28 12:14 -------
Hello,
The PropertyConfigurator.configureAndWatch method is unsafe because it
never cleans up after the watchdog thread. This method will be removed
in future log4j versions. Please do not use
PropertyConfigurator.configureAndWatch.
I am closing and marking this bug as invalid. Note that this does not
mean that there aren't any other problems with
DailyRollingFileAppender. They will be addressed separately. Thank you
for your understanding.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org