Our application sends the contents of the derby.log file to our server whenever Apache Derby throws a SQLException in our application.
To get detailed logs, we set the 'derby.infolog.append' property to true.
However, we notice extremely large log files, since the logs also contain boot output every time a connection is made to the database.
NOTE: we use Derby in native mode.
Is there a way to limit the derby to the total number of lines that it writes to the derby.log file?
For example, it only logs the most recent 1000 lines of logs and then overwrites the oldest entries.
Our goal is to get useful debugging information from end users, but so that the log files do not grow to unmanageable sizes.
Thanks in advance,
Jim
source
share