db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-700) Derby does not prevent dual boot of database from different classloaders on Linux
Date Thu, 10 Nov 2005 21:38:03 GMT
Derby does not prevent dual boot of database from different classloaders on Linux
---------------------------------------------------------------------------------

         Key: DERBY-700
         URL: http://issues.apache.org/jira/browse/DERBY-700
     Project: Derby
        Type: Bug
    Versions: 10.1.2.1    
    Reporter: Kathey Marsden
     Fix For: 10.1.3.0


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 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.




-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message