db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Bergquist (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (DERBY-6350) Provide a rolling file implementation of derby.log
Date Mon, 23 Sep 2013 18:56:02 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13775540#comment-13775540
] 

Brett Bergquist edited comment on DERBY-6350 at 9/23/13 6:56 PM:
-----------------------------------------------------------------

Second patch attempt.  This introduces a "derby.stream.error.style" property which when set
to "rollingFile" will trigger the rolling file implementation to invoked.

This patch also removes the swallowing of any IOException or SecurityException thrown by the
RollingFileStream.  The exception will be propagated and the default "derby.log" implementation
will be used and the error logged.
                
      was (Author: bbergquist):
    Second patch attempt.  This introduces a "derby.stream.error.style" property which when
set to "rollingFile" will trigger the rolling file implementation to invoked.

This patch also removes the swallowing of any IOException or SecurityException throws by the
RollingFileStream.  The exception will be propagated and the default "derby.log" implementation
will be used and the error logged.
                  
> 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

Mime
View raw message