Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 97772 invoked from network); 23 Nov 2006 12:38:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 Nov 2006 12:38:56 -0000 Received: (qmail 15167 invoked by uid 500); 23 Nov 2006 12:39:05 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 14885 invoked by uid 500); 23 Nov 2006 12:39:03 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 14873 invoked by uid 99); 23 Nov 2006 12:39:03 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Nov 2006 04:39:03 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [192.18.1.36] (HELO gmp-ea-fw-1.sun.com) (192.18.1.36) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Nov 2006 04:38:50 -0800 Received: from d1-emea-09.sun.com ([192.18.2.119]) by gmp-ea-fw-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id kANCcShG011108 for ; Thu, 23 Nov 2006 12:38:28 GMT Received: from conversion-daemon.d1-emea-09.sun.com by d1-emea-09.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0J9600I01OFSAM00@d1-emea-09.sun.com> (original mail from John.Embretsen@Sun.COM) for derby-user@db.apache.org; Thu, 23 Nov 2006 12:38:28 +0000 (GMT) Received: from [129.159.112.236] by d1-emea-09.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0J9600M9LOG30K1A@d1-emea-09.sun.com> for derby-user@db.apache.org; Thu, 23 Nov 2006 12:38:27 +0000 (GMT) Date: Thu, 23 Nov 2006 13:36:09 +0100 From: John Embretsen Subject: Re: Derby multiple connections issue In-reply-to: <7507293.post@talk.nabble.com> Sender: John.Embretsen@Sun.COM To: Derby Discussion Reply-to: Derby Discussion Message-id: <456595B9.30100@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT References: <7507293.post@talk.nabble.com> User-Agent: Thunderbird 1.5.0.5 (X11/20060730) X-Virus-Checked: Checked by ClamAV on apache.org jatintrivedi wrote: > I have SQL Explorer plugin in Eclipse through which I can view the derby. > However when my apllication hosted on Apache (and debuggin in Eclipse) is > accessing derby database, I am not able to connect to SQL Explorer through > Eclipse and vice-versa. > There could be some issue with multiple connections to Derby This is just a wild guess, since I do not have experience with the Eclipse plugin, nor am I sure what you mean by "hosted on Apache", but it could be because Derby does not allow a database to be booted from two different JVMs at the same time. If you use the embedded driver both places, this would be the case. This is from the Developer's guide, http://db.apache.org/derby/docs/dev/devguide/cdevdvlp20458.html: Derby allows you to boot databases that are not in the system directory. While this might seem more convenient, check that you do not boot the same database with two JVMs. If you need to access a single database from more than one JVM, you will need to put a server solution in place. You can allow multiple JVMs that need to access that database to connect to the server. The Derby Network Server is provided as a server solution. See the Derby Server and Administration Guide for more information on the Network Server. In other words, a Derby database can be accessed from two JVMs if you use a client/server solution. If you use the embedded driver without starting the server, you can only access a database from one JVM at a time. However, multiple connections from one JVM is supported in all cases. -- John