Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <5728332.1179874821628.JavaMail.jira@brutus>
Date: Tue, 22 May 2007 16:00:21 -0700 (PDT)
From: "Suresh Thalamati (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-700) Derby does not prevent dual boot of
 database from different classloaders on Linux
In-Reply-To: <1202629995.1131658683294.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/DERBY-700?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498050 ]=20

Suresh Thalamati commented on DERBY-700:
----------------------------------------

[ Show =C2=BB ] Kathey Marsden [22/May/07 03:22 PM] Thanks Suresh for the p=
atch! I was wondering, why do we need=20
setContextClassLoader privileges for derby.jar with the change?=20

I must have added that permission while debugging to run the test under sec=
urity manager.=20
Only security permission that is required for derby.jar  is read/write  of =
derby.storage.jvmInstanceID=20
property.

Thanks for for volunteering to fix the bug, Kathey.
.


> Derby does not prevent dual boot of database from different classloaders =
on Linux
> -------------------------------------------------------------------------=
--------
>
>                 Key: DERBY-700
>                 URL: https://issues.apache.org/jira/browse/DERBY-700
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>    Affects Versions: 10.1.2.1
>         Environment: ava -version
> java version "1.4.2_08"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_08-b03)
> Java HotSpot(TM) Client VM (build 1.4.2_08-b03, mixed mode)
>            Reporter: Kathey Marsden
>         Assigned To: Kathey Marsden
>            Priority: Critical
>         Attachments: DERBY-700.diff, DERBY-700.stat, DERBY-700_v1_use_to_=
run_DualBootrepro_multithreaded.diff, DERBY-700_v1_use_to_run_DualBootrepro=
_multithreaded.stat, derby700_singleproperty_v1.diff, derby700_singleproper=
ty_v1.stat, DualBootRepro.java, DualBootRepro2.zip, DualBootRepro_mutltithr=
eaded.tar.bz2
>
>
> Derby does not prevent dual boot from two different classloaders on Linux=
.
> To reproduce run the  program DualBootRepro with no derby jars in your cl=
asspath. The program assumes derby.jar is in 10.1.2.1/derby.jar, you can ch=
ange the location by changing the DERBY_LIB_DIR variable.
> On Linux the output is:
> $java -cp . DualBootRepro
> Loading derby from file:10.1.2.1/derby.jar
> 10.1.2.1/derby.jar
> Booted database in loader java.net.URLClassLoader@8ed465
> FAIL: Booted database in 2nd loader java.net.URLClassLoader@dc6a77
> On Windows I get the expected output.
> $ java -cp . DualBootRepro
> Loading derby from file:10.1.2.1/derby.jar
> 10.1.2.1/derby.jar
> Booted database in loader java.net.URLClassLoader@1ac04e8
> PASS: Expected exception for dualboot:Another instance of Derby may have =
already booted the database D:\marsden\repro\dualboot\mydb.

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.