You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Myrna van Lunteren <m....@gmail.com> on 2009/04/14 06:01:22 UTC

Re: [jira] Commented: (DERBY-4147) DerbyServer shutdown unexpected after running for some days

On Mon, Apr 13, 2009 at 8:49 PM, Dennis Cheung (JIRA) <ji...@apache.org> wrote:
>
>    [ https://issues.apache.org/jira/browse/DERBY-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12698637#action_12698637 ]
>
> Dennis Cheung commented on DERBY-4147:
> --------------------------------------
>
> It was down again and I checked the log file.
>
> derby.log does not contain any error message.
>
> I don't know what was being execeuted as there are many running progress.
>
In the directory where you start network server (likely where
derby.log gets created) please create a file called 'derby.properties'
with the following contents:
derby.stream.error.logSeverityLevel=0
derby.language.logStatementText=true
derby.infolog.append=true

This should make derby put a lot of information into derby.log -
likely more than you need.
You may need to monitor derby.log then and empty it when it starts
taking up too much disk space without any errors.

HTH
Myrna