[ https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484550 ]
Suresh Thalamati commented on DERBY-700: ---------------------------------------- While reading comments for this issue yet again, noticed Rick mentioned long time ago , it might be possible to make Derby jdbc driver hold a state that is global to jvm, not specific to a class loader. Is that how it really works even if the user loads the driver using class loaders ? Basically , is it possible to make org.apache.derby.jdbc.EmbeddedDriver.java statically initialize an JVMID(a UUID) that can be accessed from any class loader ? > 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 > 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, DualBootRepro.java, > DualBootRepro2.zip, DualBootRepro_mutltithreaded.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 > classpath. The program assumes derby.jar is in 10.1.2.1/derby.jar, you can > change 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 [EMAIL PROTECTED] > FAIL: Booted database in 2nd loader [EMAIL PROTECTED] > 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 [EMAIL PROTECTED] > PASS: Expected exception for dualboot:Another instance of Derby may have > already booted the database D:\marsden\repro\dualboot\mydb. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.