[logback-dev] [JIRA] Updated: (LBCORE-166) RenameUtil not truncating file if delete fails during rollover
Jose David Barrio (JIRA)
noreply-jira at qos.ch
Thu Sep 2 13:37:16 CEST 2010
[ http://jira.qos.ch/browse/LBCORE-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jose David Barrio updated LBCORE-166:
-------------------------------------
Attachment: RenameUtil.patch
> 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
More information about the logback-dev
mailing list