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 (nike.apache.org: domain of
 Clint.Gilbert@childrens.harvard.edu designates 134.174.20.64 as permitted
 sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: Derby in Tomcat webapps
Date: Thu, 29 May 2008 12:34:45 -0400
Message-ID: <F848171C7BAF8A4993C209C5B1422D9E01D44BA5@CHEXV2.CHBOSTON.ORG>
Thread-Topic: Derby in Tomcat webapps
Thread-Index: AcjBpsCXs1sLYLODRXO8oqytXdMcPQAALTDj
References: <5627810d0805290855o59d140e9uddd1f0355f11b24b@mail.gmail.com>
 <d46327c70805290911j22ee53deo3e022f08c6d18f12@mail.gmail.com>
From: "Gilbert, Clint" <Clint.Gilbert@childrens.harvard.edu>
To: "Derby Discussion" <derby-user@db.apache.org>,
	"Derby Discussion" <derby-user@db.apache.org>
Content-Type: text/plain;
 charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

For what it's worth, I had a problem similar to the original poster's.  =
Upon restarting Tomcat, my embedded Derby DB would occasionally boot =
read-only, or not at all - a problem on a development server that was =
bounced frequently.  This was using Hibernate and its built-in =
connection pooling.  It seemed that the DB was never getting properly =
shut down. =20

I solved the problem by running the Derby network server on my local =
machine and making connections to that instead of the embedded DB.  =
That's a lot less slick, however, so I plan to try using a "real" JNDI =
datasource in the future.


-----Original Message-----
From: Robert J. Carr [mailto:rjcarr@gmail.com]
Sent: Thu 5/29/2008 12:11 PM
To: Derby Discussion
Subject: Re: Derby in Tomcat webapps
=20
> 1. When I unload and then reload the app, the new instance of the app =
can't
> start the database. I have to stop and then start Tomcat.

My application runs in tomcat and I can deploy and undeploy my app and
the database is fine and I'm able to reconnect.  Are you unloading the
database when you undeploy?

> 2. When I try to run a second app that uses Tomcat, it can't start the
> database.

If you are using embedded derby, as far as I know, you can only have
one active connection to it at a time.

You might be able to get around this using JNDI data sources, which I
think ties the connection to tomcat and not to your application.  I
haven't confirmed this, but it is worth a shot if you're not already
doing it (and a better practice as well).

Good luck!