You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by de...@db.apache.org on 2004/10/15 01:51:52 UTC

[jira] Closed: (DERBY-32) Logic to prevent mutiple jvms booting the same database in parallel to avoid accidental corruptions on Unix environment is not working.

Message:

   The following issue has been closed.

   Resolver: Samuel Andrew McIntyre
       Date: Thu, 14 Oct 2004 4:49 PM

svn commit 54681
---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/DERBY-32

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: DERBY-32
    Summary: Logic to prevent mutiple jvms  booting the same  database  in parallel  to avoid accidental corruptions on  Unix environment is not working.
       Type: Bug

     Status: Closed
   Priority: Minor
 Resolution: FIXED

    Project: Derby
 Components: 
             Store
   Fix Fors:
             10.0.2.0
   Versions:
             10.0.2.0

   Assignee: Suresh Thalamati
   Reporter: Suresh Thalamati

    Created: Tue, 5 Oct 2004 4:50 PM
    Updated: Thu, 14 Oct 2004 4:49 PM
Environment: Unix Environment(Solaris. Linux ..etc) 

Description:
Current architecure requires that only one JVM boots a database at a time. If more than one JVM boots the same database, unrecoverable courruptions can occur. To avoid users accidentaly getting into this 
scenario,  Derby catches this case and throws error: For example
On windows if two jvm's boot the same database it throws the following error: ERROR XSDB6: Another instance of Derby may have already booted the database C:\s
uresht\databases\wombat.
--

On Solaris , this logic seems to have broken; It allows multiple 
jvm's to boot the same database. 

On Linux it holds on to the lock even if database is shutdown. 
  
Repro:
Connect to the same database in parallel using two jvms through ij. 

 



---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira