You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Kim Haase (JIRA)" <ji...@apache.org> on 2013/09/30 22:05:29 UTC

[jira] [Created] (DERBY-6360) Document rolling file implementation of derby.log

Kim Haase created DERBY-6360:
--------------------------------

             Summary: Document rolling file implementation of derby.log
                 Key: DERBY-6360
                 URL: https://issues.apache.org/jira/browse/DERBY-6360
             Project: Derby
          Issue Type: Bug
          Components: Documentation
    Affects Versions: 10.11.0.0
            Reporter: Kim Haase
            Assignee: Kim Haase


The new rolling log file feature implemented by DERBY-6350 needs to be documented in the reference manual. This is the information provided on 23 September -- please let me know if it needs updating.

derby.stream.error.style=rollingFile -> triggers the rolling file implementation and takes precedence over derby.stream.error.file or derby.stream.error.field or derby.stream.error.method

derby.stream.error.rollingFile.pattern=<default is %d/derby-%g.log which creates files 'derby-0.log, derby-1.log, etc. in the directory where 'derby.system.home' points to>
derby.stream.error.rollingFile.limit=<defaults to 1024000 bytes>
derby.stream.error.rollingFile.count=<defaults to 10 files>

Note that the "derby.infolog.append" is still honored. If set to "false", then when Derby starts, the log files are rolled immediately and a new log file is used. If set to "true", then when Derby starts, the existing newest log file (if any) is appended to.




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