[
https://issues.apache.org/jira/browse/DERBY-6350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13778268#comment-13778268
]
Brett Bergquist commented on DERBY-6350:
----------------------------------------
You are not doing anything wrong Mamta, I did something wrong. I wrongly
assumed that "derby.system.home" property would always be set. The default for
this uses a patter of "%d/derby-%g.log". The "%d" indicates that the rolling
log file should be in the directory pointed to by 'derby.system.home' system
property. I did my testing with the network server startup of derby and it
seems that the embedded start as from IJ does not set this property.
I see in your output 'derby.syste.home=null' which gave the clue.
I will have to investigate more to determine how to reliably find where the
directory where the log file should be located.
As a test, I started IJ after setting
DERBY_OPTS="-Dderby.system.home=/Users/brett/derby" and then IJ worked
correctly.
> 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
