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] [Created] (DERBY-6350) Provide a rolling file implementation of derby.log
Date Thu, 19 Sep 2013 19:24:03 GMT
Brett Bergquist created DERBY-6350:
--------------------------------------

             Summary: 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


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