db-derby-dev mailing list archives

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

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

Stan Bradbury commented on DERBY-2944:
--------------------------------------

Hi Aaron -
I have no problem running two versions or two instances of the same version in different classloaders
in the same VM.  Just be careful not to double boot a database.  What problems are you experiencing?

> 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