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 (athena.apache.org: local policy)
MIME-version: 1.0
Content-transfer-encoding: 8BIT
Content-type: text/plain; format=flowed; charset=windows-1252
Date: Tue, 28 Jul 2009 08:39:10 +0200
From: Kristian Waagan <Kristian.Waagan@Sun.COM>
Subject: Re: Embedded Derby multi-user
In-reply-to: 
 <C02A47E990DE164EB17E7F7E15182615035344AB@logimail1.LogiXML.local>
Sender: Kristian.Waagan@Sun.COM
To: Derby Discussion <derby-user@db.apache.org>
Message-id: <4A6E9D0E.3000403@Sun.COM>
References: <C02A47E990DE164EB17E7F7E15182615035344AB@logimail1.LogiXML.local>
User-Agent: Thunderbird 2.0.0.21 (X11/20090623)

Clifton B. Sothoron Jr. wrote:
>
> I�m creating an application which receives various requests to insert, 
> update and query an Embedded Derby database. It works properly except 
> when one request does a lot of inserts. During this time query 
> requests are blocked. I get the message edules' not found. --- 
> �org.apache.derby.impl.jdbc.EmbedSQLException: Database 
> 'C:\rdScheduler\Schedules' not found.� Once the inserts are done then 
> queries work. I�ve been rooting around the derby.properties 
> documentation. It isn�t clear to me how to use this file to configure 
> Derby to allow concurrent access. How is this done?
>

Hello Clifton,

Derby allows concurrent access by default, by using multiple connections 
to the database. Note that only one JVM can have the database booted at 
a time. If you need to access the database concurrently from several 
JVMs, you have to use the network server.

The message you posted indicates that the database you are trying to 
connect to doesn't exist. Is there anything else printed to your logs, 
or maybe in the file derby.log?

Just so we're on the same page here;
- Are you accessing the database with several connections from a single 
JVM, using the embedded driver?
- Are you sure you are not trying to boot the same database from 
different JVMs?
- Where in your application does the error occur; during connect or 
during processing?
- Which version of Derby are you using?

The answers to these questions may bring us closer to finding the 
problem. Also, please post the stack trace for the error if you have it 
available.


Regards,
-- 
Kristian
>
> TIA,
>
> Clifton Sothoron
>
> LogiXML, Development Department
> Clifton.SothoronJr@logixml.com <mailto:kelly@logixml.com> | 
> http://www.logixml.com <blocked::blocked::http://www.logixml.com/>
>