[ http://jira.qos.ch/browse/LBCORE-166?page=com.atlassian.jira.plugin.system.i... ] manas kelshikar commented on LBCORE-166: ---------------------------------------- We have also experienced this issue while using dm server on windows. In our case we are using a RollingFileAppender with FixedWindowRollingPolicy and SizeBasedTriggeringPolicy so when a rename failure is followed by a delete failure there is a 'continuous' copy of the file leading to massive system I/O. This is a pretty severe problem and its priority should be bumped up from Minor. I will update the bug with logback configuration and also with output from an attached statuslistener.
RenameUtil not truncating file if delete fails during rollover --------------------------------------------------------------
Key: LBCORE-166 URL: http://jira.qos.ch/browse/LBCORE-166 Project: logback-core Issue Type: Bug Components: Rolling Affects Versions: 0.9.24 Environment: Microsoft Windows XP SP2 OAS 10.1.3.4 Java 1.5.0_14 Reporter: Jose David Barrio Assignee: Logback dev list Priority: Minor Attachments: RenameUtil.patch
When using logback under Windows over Oracle Application Server, if you redeploy the web application, the log file is keep open by some reason so when a new rollover happens it fails to rename the log file. Currently RenameUtil does: - Try to rename log file. - If rename fails then rename by copy (copy plus delete). If for some reason deletion fails the log file keeps all its content so I just added a truncate if deletion fails: - Try to rename log file. - If rename fails then rename by copy (copy plus delete). - If delete fails then truncate file. I do have a patch file if it's useful.
-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira