Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: <41E2F594.9020707@comcast.net>
Date: Mon, 10 Jan 2005 15:37:24 -0600
From: Barnet Wagman <b.wagman@comcast.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040114
MIME-Version: 1.0
To: Derby Discussion <derby-user@db.apache.org>
Subject: Re: Can a connection expire?
References: <41E1C4EC.6030606@comcast.net> <41E2DC0B.4090700@Sourcery.Org>
In-Reply-To: <41E2DC0B.4090700@Sourcery.Org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Satheesh Bandaram wrote:

>I don't think a connection expires in embedded Derby.  Could it be
>possible a severe error was encountered during the INSERTs that might
>have caused the connection to close? Was there any info in the
>derby.log? This log file should get created in the SYSTEM_HOME location.
>
>  
>
I think your right, something appears to be causing the connection to 
close, but there's nothing in my log file.  Actually, I can't find a 
derby.log file at all.  By default, it SYSTEM_HOME the directory where 
the database resides?  I was using vanilla installation of embedded 
Derby. I've tried recreating the database with logDevice explicitly set, 
but I'm still not getting a derby.log file.  Do I need to do something 
explicit to get one?

Thanks