[
https://issues.apache.org/jira/browse/DERBY-6350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13773856#comment-13773856
]
Brett Bergquist commented on DERBY-6350:
----------------------------------------
I think you are saying the same thing that Rick suggested and now there are two
:) So I think following Rick's suggestion and use something like:
derby.stream.error=rollingFile
is preferrable as this will trigger the rolling file implementation. Then the
properties:
derby.stream.error.rollingFile.pattern=
derby.stream.error.rollingFile.limit=
derby.stream.error.rollingFile.count=
can be used to customize the rolling file but if not present the default values
will be used. Also probably another property:
derby.stream.error.rollingFile.append=<true|false>
which will act like the "derby.infolog.append" in that the existing log file
will be append to at startup if "true" or the files will be rolled and a new
log file will be created if "false" or do you think that "derby.infolog.append"
is sufficient to serve as this knob?
If we can agree on these, I will make the change and submit a patch with this
change.
> 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
>
>
> 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
