[
https://issues.apache.org/jira/browse/DERBY-6350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13797186#comment-13797186
]
Myrna van Lunteren edited comment on DERBY-6350 at 10/16/13 8:00 PM:
---------------------------------------------------------------------
I agree - the derby.log file creation is not something that's under control of
the ErrorStreamTest, it is something related to our junit framework and basic
derby operation as Brett identified rather than this feature.
I ran the engine._Suite (which includes the new test fixtures) with patch _7
applied, and it now indeed passes on my windows machine.
Further improvements can be done separately, (under separate JIRAs, like what
Mamta found for failure analysis of DERBY-6380), I think this feature is now
ready to go in.
+1 to commit.
was (Author: myrna):
I agree - the derby.log file creation is not something that's under control of
the ErrorStreamTest, it is something related to our junit framework rather than
this feature.
I ran the engine._Suite (which includes the new test fixtures) with patch _7
applied, and it now indeed passes on my windows machine.
Further improvements can be done separately, (under separate JIRAs, like what
Mamta found for failure analysis of DERBY-6380), I think this feature is now
ready to go in.
+1 to commit.
> 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, rolling_file_patch_7.diff
>
>
> 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)
