From derby-dev-return-25785-apmail-db-derby-dev-archive=db.apache.org@db.apache.org Thu Aug 03 16:52:30 2006 Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 95841 invoked from network); 3 Aug 2006 16:52:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 3 Aug 2006 16:52:30 -0000 Received: (qmail 77395 invoked by uid 500); 3 Aug 2006 16:52:29 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 77367 invoked by uid 500); 3 Aug 2006 16:52:29 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 77358 invoked by uid 99); 3 Aug 2006 16:52:28 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Aug 2006 09:52:28 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [32.97.182.142] (HELO e2.ny.us.ibm.com) (32.97.182.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Aug 2006 09:52:27 -0700 Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by e2.ny.us.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k73Gq6ZP004399 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Thu, 3 Aug 2006 12:52:06 -0400 Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay04.pok.ibm.com (8.13.6/NCO/VER7.0) with ESMTP id k73Gq61N292518 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 3 Aug 2006 12:52:06 -0400 Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id k73Gq6jT009980 for ; Thu, 3 Aug 2006 12:52:06 -0400 Received: from [127.0.0.1] (sig-9-65-16-72.mts.ibm.com [9.65.16.72]) by d01av03.pok.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k73Gq4T5009880 for ; Thu, 3 Aug 2006 12:52:06 -0400 Message-ID: <44D229B3.8040004@sbcglobal.net> Date: Thu, 03 Aug 2006 09:52:03 -0700 From: Mike Matrigali Reply-To: mikem_app@sbcglobal.net User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: derby-dev@db.apache.org Subject: Re: [jira] Updated: (DERBY-700) Derby does not prevent dual boot of database from different classloaders on Linux References: <4867349.1154609056094.JavaMail.jira@brutus> <44D2223B.9050001@sbcglobal.net> <44D2260C.9020809@apache.org> In-Reply-To: <44D2260C.9020809@apache.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N great, sounds like the sync part is a non-issue. I was stuck trying to come up with something specific to the db shared across both classloaders that we could sync on. Using this will single thread opens of different dbs, but I think that is ok. Daniel John Debrunner wrote: > Mike Matrigali wrote: > > > >>If anyone has ideas on this one, please post them. I have been stumped >>by this one so far. As I posted earlier I think one approach simply >>needs a way to uniquely identify the current JVM, and also some way >>to coordinate a sync block across 2 class loaders. > > > A Java synchronized block across class loaders is easy, either > of these will work. But I'm not sure if that's what you really meant, > but I'd thought I'd throw it out there. > > synchronized ("derby") > { > } > > synchronized ("") > { > } > > Dan. > > > >