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

Alex Rudyy resolved QPID-6614.
------------------------------
    Resolution: Fixed

Changes are reviewed whilst working in pair with Lorenz

> [Java Broker] Make BrokerFileLogger implementation expose content of the 
> current file and the names/content of any previously rolled files
> ------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-6614
>                 URL: https://issues.apache.org/jira/browse/QPID-6614
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>            Reporter: Alex Rudyy
>            Assignee: Alex Rudyy
>             Fix For: qpid-java-6.0
>
>         Attachments: 
> 0001-Fix-RolloverFileAppenderFactory-to-start-triggering-.patch, 
> 0001-QPID-6614-Java-Broker- 
> Add-onNoRolloverDetected-to-RolloverListener.patch, 
> 0002-QPID-6614-Improve-functionality-around-exposing-log-.patch
>
>
> Add a derived attribute BrokerFileLogger#rolledFiles that exposed a list of 
> filenames  that were previously rolled by the appender:
> * At open time, the implementation must check for any pre-existing rolled 
> files that potentially match the rolling specification, taking into account 
> date or sized based rolling (or the possibility of compression).  The 
> implementation does not need to consider that the configuration may have 
> changed, nor does it need to consider the possibility that another actor 
> adding a file to the file system at runtime.
> * At runtime if rollover occurs, the derived attribute needs refresh itself.  
> * The content of rolledFiles should be in the same terms of the effective 
> value of getFile() - which may be absolute or relative.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to