[jira] [Comment Edited] (DERBY-6350) Provide a rolling file implementation of derby.log

["Myrna van Lunteren (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DERBY-6350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13790748#comment-13790748 ] 

Myrna van Lunteren edited comment on DERBY-6350 at 10/9/13 7:24 PM:
--------------------------------------------------------------------

I've not had a chance to further investigate either, except to say that there are 3 fixtures/methods that suffer from this behavior:
testStyleRollingFile()
testDefaultRollingDefaultConfig()
testDefaultRollingUserConfig()
(so the other failures were cascading from this).

I prevented these 3 fixtures from running (by renaming the methods to start with 'xtest' instead of 'test'), and ErrorStreamTest passed, and the engine._Suite suite passed also.

Windows is pickier about deleting files that have been accessed, we've seen that before, so this could just be a test cleanup issue...


was (Author: myrna):
I've not had a chance to further investigate either, except to say that there are 3 fixtures/methods that suffer from this behavior:
testStyleRollingFile()
testDefaultRollingDefaultConfig()
testDefaultRollingUserConfig()
(so the other failures were cascading from this).

I prevented these fixtures 3 from running (by renaming the methods to start with 'xtest' instead of 'test'), and ErrorStreamTest passed, and the engine._Suite suite passed also.

Windows is pickier about deleting files that have been accessed, we've seen that before, so this could just be a test cleanup issue...

> Provide a rolling file implementation of derby.log
> --------------------------------------------------
>
>                 Key: DERBY-6350
>                 URL: https://issues.apache.org/jira/browse/DERBY-6350
>             Project: Derby
>          Issue Type: Improvement
>          Components: Miscellaneous
>            Reporter: Brett Bergquist
>            Assignee: Brett Bergquist
>            Priority: Minor
>              Labels: features
>         Attachments: rollingfilelog.patch.txt, rollingfilelog.patch.txt, rolling_file_patch_5.txt, rolling_file_patch_6.txt
>
>
> By default, derby.log grows without bounds if the derby.infolog.append property is set to "true".   Setting this to "true" helps in a hands off production environment to ensure that if Derby restarts, the derby.log which might contain important information is not lost.  On the other hand, when set the "true" the derby.log grows without bounds.  This is problematic in a long running system.  
> What is really needed is the ability to have a rolling derby.log file support where the maximum file size and maximum number of files can be specified.  Derby has the ability to configure the location of the log file (ie. derby.stream.error.file) and also two methods of redirecting the error stream (.ie derby.stream.error.method and derby.stream.error.field).  There is no standard implementation that supports a rolling derby.log however.
> This facility should be part of the core Derby system so that it works in both embedded and network server models.



--
This message was sent by Atlassian JIRA
(v6.1#6144)