You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@qpid.apache.org by "Justin Ross (JIRA)" <ji...@apache.org> on 2016/12/09 20:06:58 UTC

[jira] [Updated] (QPID-2739) QpidRollingFileAppender does not delete backup files.

     [ https://issues.apache.org/jira/browse/QPID-2739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Ross updated QPID-2739:
------------------------------
    Component/s: Java Broker

> QpidRollingFileAppender does not delete backup files.
> -----------------------------------------------------
>
>                 Key: QPID-2739
>                 URL: https://issues.apache.org/jira/browse/QPID-2739
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: M4, 0.5, 0.6
>            Reporter: Martin Ritchie
>
> Currently the QpidRollingFileAppender behaves like the log4j RollingFileAppender wrt maintaining a maximum number of backup files. 
> When a file is to be deleted the file with relative path is provided to the delete method. Trouble is we have augmented RollingFileAppender to provide a backup loaction. This means that the deleteFile method fails to delete the file as the main Appender code does not know about the backup location.
> Augmenting the delete method to change the path would be in line with the addition to add the compression file extension that is already performed here.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org