Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (nike.apache.org: domain of m.v.lunteren@gmail.com
 designates 209.85.146.176 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=BfAGeU0ObLx894c1IyrBu/PnrtfwPjxoC3iNrGpz6ozafWwUspNQeY0VmulzpRbmxT
         XKrhV2qf0zfG78r2qRLzuEz54pHyjBVMJdPo0GYftFeFNAXVPvUkv4D29McZAhV0wXmU
         +VJfmgyz0jMQQFWjY6jqCWg2IGPO0V47Bsk0Y=
MIME-Version: 1.0
In-Reply-To: <250438840.1239680954952.JavaMail.jira@brutus>
References: <1733375932.1238989212913.JavaMail.jira@brutus>
	 <250438840.1239680954952.JavaMail.jira@brutus>
Date: Mon, 13 Apr 2009 21:01:22 -0700
Message-ID: <c25576af0904132101r575ce348l5ae89c5e8249f768@mail.gmail.com>
Subject: Re: [jira] Commented: (DERBY-4147) DerbyServer shutdown unexpected
	after running for some days
From: Myrna van Lunteren <m.v.lunteren@gmail.com>
To: derby-dev@db.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Mon, Apr 13, 2009 at 8:49 PM, Dennis Cheung (JIRA) <jira@apache.org> wro=
te:
>
> =A0 =A0[ https://issues.apache.org/jira/browse/DERBY-4147?page=3Dcom.atla=
ssian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=
=3D12698637#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=3D0
derby.language.logStatementText=3Dtrue
derby.infolog.append=3Dtrue

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