[
https://issues.apache.org/jira/browse/DERBY-6350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13778031#comment-13778031
]
Mamta A. Satoor commented on DERBY-6350:
----------------------------------------
Brett, may be I am doing something wrong, but in derby.properties, I only
specified(I want to use the default for other associated properties)
derby.stream.error.style=rollingFile
But following ij session prints a NPE and there is no log file created. May be
some of the other associated properties are not optional. I wonder if we throw
the exception because of some problem with using the rolling log, we should
print the stack trace on std err.
$ java -Dderby.language.logQueryPlan=true -Dij.exceptionTrace=true
org.apache.derby.tools.ij
ij version 10.11
ij> Wed Sep 25 13:23:16 PDT 2013 Thread[main,5,main]
java.lang.NullPointerException
----------------------------------------------------------------
Wed Sep 25 13:23:17 PDT 2013:
Booting Derby version The Apache Software Foundation - Apache Derby - 10.11.0.0
alpha - (1): instance a816c00e-0141-56ca-3f03-000000205398
on database directory C:\p4clients\svnmain\client3\trunk\systest\out142\db1
with class loader sun.misc.Launcher$AppClassLoader@53745374
Loaded from file:/C:/p4clients/svnmain/client3/trunk/classes/
java.vendor=IBM Corporation
java.runtime.version=pwi3260sr14-20130705_01 (SR14)
java.fullversion=JRE 1.6.0 IBM J9 2.4 Windows 7 x86-32
jvmwi3260sr14-20130704_155156 (JIT enabled, AOT enabled)
J9VM - 20130704_155156
JIT - r9_20130517_38390
GC - GA24_Java6_SR14_20130704_1138_B155156
user.dir=C:\p4clients\svnmain\client3\trunk\systest\out142
os.name=Windows 7
os.arch=x86
os.version=6.1 build 7601 Service Pack 1
derby.system.home=null
derby.stream.error.style=rollingFile
Database Class Loader started - derby.database.classpath=''
> 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
