Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-2944

Derby doesn't allow more than one instance per VM

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 10.2.2.0
    • 10.2.2.0
    • Miscellaneous
    • None

    Description

      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.

      Attachments

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            digulla Aaron Digulla
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment