db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2944) Derby doesn't allow more than one instance per VM
Date Tue, 17 Jul 2007 15:26:04 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513275
] 

Daniel John Debrunner commented on DERBY-2944:
----------------------------------------------

I think this is a bug (lack of feature) in the tool. Different versions of derby can be booted
and shutdown within the same jvm (with different class loaders).
Derby's upgrade tests do this.

The mechanism to shutdown the embedded driver is to request a connection with the URL

   "jdbc:derby:;shutdown=true"

or to set the 'shutdownDatabase'Java bean property on the embedded data sources to 'shutdown'



> Derby doesn't allow more than one instance per VM
> -------------------------------------------------
>
>                 Key: DERBY-2944
>                 URL: https://issues.apache.org/jira/browse/DERBY-2944
>             Project: Derby
>          Issue Type: Bug
>          Components: Miscellaneous
>    Affects Versions: 10.2.2.0
>            Reporter: Aaron Digulla
>
> If you have an IDE or a DB tool, you cannot dynamically load/unload the embedded derby
driver.
> In Eclipse BIRT, this created the following situation: The examples use Derby 10.1. My
application uses 10.2. I can't switch between the examples and the reports in my application
without restarting Eclipse and patching the Derby plugin.
> It would be great if you could add a method which we could call to cleanup the embedded
driver so we can throw the classloader away and load another instance of Derby.

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


Mime
View raw message