[logback-dev] [JIRA] Updated: (LBCORE-166) RenameUtil not truncating file if delete fails during rollover

[manas kelshikar (JIRA)]

     [ http://jira.qos.ch/browse/LBCORE-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

manas kelshikar updated LBCORE-166:
-----------------------------------

    Attachment: logbackStatus.txt

The pasted pattern is repeated a few times in the logs. SInce this was a test run with atleast a 50times less load than our load test environment logback seems to have managed to recovered and I/O came back under control very quickly. However, our load test environment was experiencing 50MB/s I/O writes which pretty much meant that the system was doing nothing but write to the filesystem.

13:58:59,075 |-WARN in c.q.l.co.rolling.helper.RenameUtil - Failed to rename file [serviceability\logs\com.test.foo.client.epapp-1.0.0\log.log] to [serviceability\logs\com.test.foo.client.epapp-1.0.0\log_1.log].
13:58:59,075 |-WARN in c.q.l.co.rolling.helper.RenameUtil - Attempting to rename by copying.
13:58:59,122 |-WARN in c.q.l.co.rolling.helper.RenameUtil - Could not delete serviceability/logs/com.test.foo.client.epapp-1.0.0/log.log

Will attache the logback config shortly.

> 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: logbackStatus.txt, 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