Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Wed, 23 Oct 2013 07:46:11 +0000 (UTC)
From: "Knut Anders Hatlen (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12669518.1379618631042.108777.1382514371990@arcas>
In-Reply-To: <JIRA.12669518.1379618631042@arcas>
References: <JIRA.12669518.1379618631042@arcas>
Subject: [jira] [Commented] (DERBY-6350) Provide a rolling file
 implementation of derby.log
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Knut Anders Hatlen commented on DERBY-6350:
-------------------------------------------

There was a failure in one of the new test cases in the latest nightly test cycle:
http://download.java.net/javadesktop/derby/request_5583094/javadb-task-3745053.html

{noformat}
junit.framework.AssertionFailedError: /localhome/tendril4.2/work/run/27530881/junit/system/derby-0.log exists
	at org.apache.derbyTesting.functionTests.tests.engine.ErrorStreamTest.assertNotExisting(ErrorStreamTest.java:697)
	at org.apache.derbyTesting.functionTests.tests.engine.ErrorStreamTest.testWrongStyle(ErrorStreamTest.java:403)
	at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:117)
	at org.apache.derbyTesting.junit.BaseJDBCTestCase.runBareOverridable(BaseJDBCTestCase.java:439)
	at org.apache.derbyTesting.junit.BaseJDBCTestCase.runBare(BaseJDBCTestCase.java:456)
{noformat}

> 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)