db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6350) Provide a rolling file implementation of derby.log
Date Tue, 01 Oct 2013 04:37:25 GMT

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

Mamta A. Satoor commented on DERBY-6350:
----------------------------------------

Brett, I debugged through SingleStream.java and see if that in case of IllegalArgumentException,
we call useDefaultStream as you pointed out. But useDefaultStream uses System.err to log the
info.
		return new BasicHeaderPrintWriter(System.err, header, false, "System.err");
I wonder in this case, if we should be calling createDefaultStream which uses derby.log. If
we do use createDefaultStream. Once we have the HeaderPrintWriter for derby.log, we can call
printlnWithHeader to log the IllegalArgumentException.

If we do make the above change, then I think we will need to check for errStreamFile to be
empty and derby.log to be not empty.

> 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)

Mime
View raw message