[
https://issues.apache.org/jira/browse/DERBY-6350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13775591#comment-13775591
]
Brett Bergquist commented on DERBY-6350:
----------------------------------------
So for documentation purposes:
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.
> 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
> Priority: Minor
> Labels: features
> Attachments: rollingfilelog.patch.txt, rollingfilelog.patch.txt
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
