db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6350) Provide a rolling file implementation of derby.log
Date Wed, 16 Oct 2013 16:59:51 GMT

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

Mamta A. Satoor commented on DERBY-6350:

Brett, I will apply your latest patch and run the junit tests on my machine. 

I had used the earlier patch to run the junit suite with rollingFile(as shown below) 
time java  -Dderby.stream.error.style=rollingFile -Dderby.tests.trace=true junit.textui.TestRunner
org.apache.derbyTesting.functionTests.suites.All > runall.out 2>&1
and saw the failure noticed by Myrna. Additionally, I saw that even though we are running
junit suite with the rollingFile, we still created derby.log(although it was empty) along
with expected derby-0.log and so on. I had not expected to see the traditional derby.log when
running with rollingFile. In addition, when a test failed, the failed directory had empty
derby.log copied but the rolling log files did not get copied. The code changes to copy the
rolling log files in case of failure probably need to go into org.apache.derbyTesting.junit.BaseTestCase:runBare()
in the "catch (Throwable running) {" section. I can open a new jira for this and link it this

> 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

View raw message