From derby-user-return-11999-apmail-db-derby-user-archive=db.apache.org@db.apache.org Wed Dec 16 23:55:16 2009 Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 63513 invoked from network); 16 Dec 2009 23:55:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 16 Dec 2009 23:55:16 -0000 Received: (qmail 41828 invoked by uid 500); 16 Dec 2009 23:55:15 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 41753 invoked by uid 500); 16 Dec 2009 23:55:15 -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 41745 invoked by uid 99); 16 Dec 2009 23:55:15 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Dec 2009 23:55:15 +0000 X-ASF-Spam-Status: No, hits=-4.0 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [216.82.250.147] (HELO mail129.messagelabs.com) (216.82.250.147) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Dec 2009 23:55:04 +0000 X-VirusChecked: Checked X-Env-Sender: dk068x@att.com X-Msg-Ref: server-8.tower-129.messagelabs.com!1261007682!37219276!1 X-StarScan-Version: 6.2.4; banners=-,-,- X-Originating-IP: [144.160.112.25] Received: (qmail 24681 invoked from network); 16 Dec 2009 23:54:42 -0000 Received: from sbcsmtp3.sbc.com (HELO tlph064.enaf.dadc.sbc.com) (144.160.112.25) by server-8.tower-129.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Dec 2009 23:54:42 -0000 Received: from enaf.dadc.sbc.com (localhost.localdomain [127.0.0.1]) by tlph064.enaf.dadc.sbc.com (8.14.3/8.14.3) with ESMTP id nBGNsfla018934 for ; Wed, 16 Dec 2009 17:54:42 -0600 Received: from td03xsmtp007.US.Cingular.Net (intexchapp01.us.cingular.net [135.179.64.45] (may be forged)) by tlph064.enaf.dadc.sbc.com (8.14.3/8.14.3) with ESMTP id nBGNscGv018886 for ; Wed, 16 Dec 2009 17:54:38 -0600 Received: from BD01XSMTP003.US.Cingular.Net ([135.163.18.44]) by td03xsmtp007.US.Cingular.Net with Microsoft SMTPSVC(6.0.3790.3959); Wed, 16 Dec 2009 17:54:38 -0600 Received: from BD01MSXMB018.US.Cingular.Net ([135.214.27.52]) by BD01XSMTP003.US.Cingular.Net with Microsoft SMTPSVC(6.0.3790.3959); Wed, 16 Dec 2009 15:54:37 -0800 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Just starting with Derby: Getting "Another instance of Derby may have already booted the database" with embedded db Date: Wed, 16 Dec 2009 15:54:36 -0800 Message-ID: In-Reply-To: <4B297065.9050701@amberpoint.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Just starting with Derby: Getting "Another instance of Derby may have already booted the database" with embedded db Thread-Index: Acp+qYqQZQYs0dtsQpafTrav8gzD3AAARO8A References: <4B297065.9050701@amberpoint.com> From: "KARR, DAVID (ATTCINW)" To: "Derby Discussion" X-OriginalArrivalTime: 16 Dec 2009 23:54:37.0458 (UTC) FILETIME=[1FFBBF20:01CA7EAB] X-Virus-Checked: Checked by ClamAV on apache.org > -----Original Message----- > From: Bryan Pendleton [mailto:bpendleton@amberpoint.com] > Sent: Wednesday, December 16, 2009 3:42 PM > To: Derby Discussion > Subject: Re: Just starting with Derby: Getting "Another instance of > Derby may have already booted the database" with embedded db >=20 > > first runs some sql through the "sql" task, then runs JUnit to run my > > test class? >=20 > If you take out the "sql" task invocation, does your script run > correctly? >=20 > If so, then I'd think this might be a bug in the SQL task, that it > isn't closing down the connection properly at the completion of its > work. >=20 > But if you still get the problem with the "sql" task removed, then it > may be that you somehow have some other process which still has the > database open. Well, without the "sql" task invocation, we'd have to carefully define what "correctly" means. When I did this, I didn't get the "another instance of derby" error, but I did get errors about missing tables (what the "sql" task is doing). I'll ask on the Ant list about the "sql" task possibly not closing its connection. If I can't get that resolved, I guess my only options are to execute the table creation DDL in my test code itself, or to use the network server. My first attempt to use the network server presented a problem in that when I start the server from Ant, it blocks the execution, even if I did "fork=3Dtrue" in the "java" execution.