Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 62181 invoked from network); 26 Jun 2007 14:24:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Jun 2007 14:24:55 -0000 Received: (qmail 16153 invoked by uid 500); 26 Jun 2007 14:24:49 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 16057 invoked by uid 500); 26 Jun 2007 14:24:48 -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 16001 invoked by uid 99); 26 Jun 2007 14:24:48 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Jun 2007 07:24:48 -0700 X-ASF-Spam-Status: No, hits=2.9 required=10.0 tests=HTML_10_20,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of erharold@gmail.com designates 64.233.166.180 as permitted sender) Received: from [64.233.166.180] (HELO py-out-1112.google.com) (64.233.166.180) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Jun 2007 07:24:43 -0700 Received: by py-out-1112.google.com with SMTP id p76so3177746pyb for ; Tue, 26 Jun 2007 07:24:21 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; b=SZWe8SR9550KW2kyv0lxRvGKPlzhFS+C/Jk59MYKp5fJQmHroyL5QuPJ24nE9tnNm8FOYCR8ua4locOM0QwvsaMFXKsL5LoalWmvfxzmlUTTjpBN70niiTw3XeP4IaIm/HXkgQ8p/itYb3SahM2QCKokznSpl+PseFIZx4/2RG0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=q6iHLEFW+2YwxMmdrrPgOEVUe0iXZIkCIDYov+WaVRSluOTp8aPSng9mp3a4V082wUNIpBfItB5HOGLMIr/Fq3XKh/yBZDUMAoy+KBnlc35J0mgdnUBF+VZosUmVE/31A1h/v9FBguhUyLT91hXEJ8aG2AsJyVcNZ8N4YQZPML0= Received: by 10.65.132.13 with SMTP id j13mr11257821qbn.1182867861838; Tue, 26 Jun 2007 07:24:21 -0700 (PDT) Received: by 10.64.201.16 with HTTP; Tue, 26 Jun 2007 07:24:21 -0700 (PDT) Message-ID: <49aa580c0706260724l68b7f395ld70b63be518477e1@mail.gmail.com> Date: Tue, 26 Jun 2007 10:24:21 -0400 From: "Elliotte Harold" To: "Derby Discussion" Subject: Derby, JUnit, Ant and fork MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_4809_31921438.1182867861809" X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_4809_31921438.1182867861809 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline My tests pass when run in Eclipse. However, when I run them in Ant I see errors like this: Another instance of Derby may have already booted the database C:\Documents and Settings\eharold\workspace\foo\build\CentralConfig.db. ERROR XSDB6: Another instance of Derby may have already booted the database C:\Documents and Settings\eharold\workspace\foo\build\CentralConfig.db. Apparently one VM is creating the DB, but not unlocking it before the next VM tries to read from it. Surprisingly changing from to does not seem to fix this. Any suggestions? Is there anything short of setting up a network server that will allow my unit tests to access the same database? -- Elliotte Rusty Harold erharold@gmail.com ------=_Part_4809_31921438.1182867861809 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline My tests pass when run in Eclipse. However, when I run them in Ant I see errors like this:

Another instance of Derby may have already booted the database C:\Documents and Settings\eharold\workspace\foo\build\CentralConfig.db.

ERROR XSDB6: Another instance of Derby may have already booted the database C:\Documents and Settings\eharold\workspace\foo\build\CentralConfig.db.

Apparently one VM is creating the DB, but not unlocking it before the next VM tries to read from it.

Surprisingly changing from <junit fork="yes"> to <junit fork="no"> does not seem to fix this.

Any suggestions? Is there anything short of setting up a network server that will allow my unit tests to access the same database?

--
Elliotte Rusty Harold
erharold@gmail.com ------=_Part_4809_31921438.1182867861809--