Sunitha Kambhampati wrote:
Øystein Grøvlen wrote:
"KM" == Kathey Marsden <[EMAIL PROTECTED]> writes:
KM> Øystein Grøvlen (JIRA) wrote:
>> [ >> This would be even more helpful if the derby.log file
was not overwritten on the next startup. (Probably a separate issue).
>> >> >> KM> The derby.infolog.append property is helpful
in this regard.
KM> http://db.apache.org/derby/docs/10.1/tuning/rtunproper13217.html
Thanks, Kathey, that is really what I need.
One concern I have is that by default, the derby.log gets overwritten on
subsequent boot. From my experience with customers, whenever there is an
issue, I always end up telling them to add this property almost every
time to see the debug logs. It is very common to see users reboot the
system if they hit an error and in this case, it is probable that
important relevant information in the derby.log is lost because it gets
overwritten ( ex - recovery issues , deadlock etc ).
I agree with you, had similar experience few times. May be this is the
reason behind the to do list item, Dynamic swap of derby.log
(http://db.apache.org/derby/DerbyToDo.html)> .
Maybe we could do something smart for derby.log , a balance between
keeping history across boots and disk space taken by the derby.logs.
Instead of overwriting the log on every reboot, a new log file can be
created if the current error log is more than 100K or so. To avoid
filling up the disk with the error log files, number of derby error
log files on the disk can be limited to 2 at any time.
Thanks
-suresht
