[
https://issues.apache.org/jira/browse/DERBY-6350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13783589#comment-13783589
]
Brett Bergquist commented on DERBY-6350:
----------------------------------------
Mamta, the other properties also use "useDefaultStream". For example, if
"derby.stream.error.field" fails, it calls "useDefaultStream", similarly if
"derby.stream.error.method" fails, it calls "userDefaultStream" and finally if
"derby.stream.error.file" fails, it also calls "useDefaultStream".
So should this be any different? I think if this should call
"createDefautStream" then the other methods should as well. If not, then this
should be consistent with those. And in any case, if specified wrong I think
it will be immediately recognized and corrected.
At this point I would rather not change this but of course I will go with what
ever is decided.
> 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,
> rolling_file_patch_5.txt, rolling_file_patch_6.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 was sent by Atlassian JIRA
(v6.1#6144)
