[ https://issues.apache.org/jira/browse/DERBY-6350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13807556#comment-13807556
]
Mamta A. Satoor commented on DERBY-6350:
----------------------------------------
Brett, the patch looks good. I will commit it.
> 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: ErrorStreamTest_rolling_file_cleanup.patch, 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)