db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Bergquist (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6359) Document rolling derby.log file feature
Date Fri, 04 Oct 2013 15:39:42 GMT

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

Brett Bergquist commented on DERBY-6359:

If configured with a derby.stream.error.rollingFile.count=1 and derby.stream.error.rollingFile.limit=0,
then in effect it is writing to one file of unlimited size, with the file being specified
by derby.stream.error.rollingFile.pattern (if present) and if not defaulting to "%d/derby-%g.log
(which will be derby-0.log in the directory of derby.system.home property or user.home property
if that is not set).

We need to document that "derby.stream.error.rollingFile.limit=0" is unlimited.   

So you probably will never want to it to be configured this way as you could just as well
not use the rolling file implementation, but if you did configure limit=1 and count=0, then
it will write to a specified file.

> Document rolling derby.log file feature
> ---------------------------------------
>                 Key: DERBY-6359
>                 URL: https://issues.apache.org/jira/browse/DERBY-6359
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>            Reporter: Brett Bergquist
>            Assignee: Kim Haase
>            Priority: Minor
>              Labels: documentation
> The rolling derby.log file feature needs to be documented.  This will be used to provide
the information necessary to do so.

This message was sent by Atlassian JIRA

View raw message