Ø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 ).
Maybe we could do something smart for derby.log , a balance between
keeping history across boots and disk space taken by the derby.logs.
Any comments ?
Sunitha.
