db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stanley Bradbury <bradb...@Mutagen.Net>
Subject Re: Lock on toursDB After App Disconnect Using org.apache.derby.jdbc.EmbeddedDriver
Date Thu, 25 Nov 2004 01:51:38 GMT
robert stephens wrote:

> I understand that the org.apache.derby.jdbc.EmbeddedDriver does not 
> support simultaneous connections to a Cloudscape database however it 
> appears that even after the Java app that was using the database 
> disconnects and quits.  See  "Interesting Experiment" in --- 3 --- below.
>
> Problem Example ---------> For example, I can connect to the example 
> "derbyDB" database from App1 and can connecto to the example "toursDB" 
> from App2 but after disconnecting and quiting both App1 and 
> App2.............App2 is never able to start by itself and connect to 
> the "derbyDB" because "once upon a time" App1 had connected to it even 
> though App1 is no longer running.
>
> I'm doing this on MacOS X so there is a possibility that since they (I 
> think) try to share the JavaVM over multiple apps it could be that the 
> Apple JavaVM was still running.

NOTE:  See responses by me and others in the Derby User Discussion area

Mime
View raw message