Derby and Plugins

For the Plug-In I am using the Derby library that gets copied in with when I select adding Hibernate Capabilities via MyEclipse menu, or when I use the 10.3.1.4 libraries from the Derby distribution.

I am using MyEclipse 6.0.1

Here is the exception

Caused by: ERROR XSDB6: Another instance of Derby may have already booted the database C:\Program Files\MyEclipse 6.0.01\eclipse\scrach.
    at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
    at org.apache.derby.impl.store.raw.data.BaseDataFileFactory.privGetJBMSLockOnDB(Unknown Source)
    at org.apache.derby.impl.store.raw.data.BaseDataFileFactory.run(Unknown Source)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.apache.derby.impl.store.raw.data.BaseDataFileFactory.getJBMSLockOnDB(Unknown Source)
    at org.apache.derby.impl.store.raw.data.BaseDataFileFactory.boot(Unknown Source)
    at org.apache.derby.impl.services.monitor.BaseMonitor.boot(Unknown Source)
    at org.apache.derby.impl.services.monitor.TopService.bootModule(Unknown Source)
    at org.apache.derby.impl.services.monitor.BaseMonitor.startModule(Unknown Source)
    at org.apache.derby.iapi.services.monitor.Monitor.bootServiceModule(Unknown Source)
    at org.apache.derby.impl.store.raw.RawStore.boot(Unknown Source)
    at org.apache.derby.impl.services.monitor.BaseMonitor.boot(Unknown Source)
    at org.apache.derby.impl.services.monitor.TopService.bootModule(Unknown Source)
    at org.apache.derby.impl.services.monitor.BaseMonitor.startModule(Unknown Source)
    at org.apache.derby.iapi.services.monitor.Monitor.bootServiceModule(Unknown Source)
    at org.apache.derby.impl.store.access.RAMAccessManager.boot(Unknown Source)
    at org.apache.derby.impl.services.monitor.BaseMonitor.boot(Unknown Source)
    at org.apache.derby.impl.services.monitor.TopService.bootModule(Unknown Source)
    at org.apache.derby.impl.services.monitor.BaseMonitor.startModule(Unknown Source)
    at org.apache.derby.iapi.services.monitor.Monitor.bootServiceModule(Unknown Source)
    at org.apache.derby.impl.db.BasicDatabase.bootStore(Unknown Source)
    at org.apache.derby.impl.db.BasicDatabase.boot(Unknown Source)
    at org.apache.derby.impl.services.monitor.BaseMonitor.boot(Unknown Source)
    at org.apache.derby.impl.services.monitor.TopService.bootModule(Unknown Source)
    at org.apache.derby.impl.services.monitor.BaseMonitor.bootService(Unknown Source)
    at org.apache.derby.impl.services.monitor.BaseMonitor.startProviderService(Unknown Source)
    at org.apache.derby.impl.services.monitor.BaseMonitor.findProviderAndStartService(Unknown Source)
    at org.apache.derby.impl.services.monitor.BaseMonitor.startPersistentService(Unknown Source)
    at org.apache.derby.iapi.services.monitor.Monitor.startPersistentService(Unknown Source)

Thanks
Frank

This just confirms what I already knew about the limitations of “non-server” usage of Derby.

My question is that when I “Close the Connection” from MyEclipse DBE, shouldn’t it be closing and shutting down the database for use? Is that a defect?

If it shuts down the database, don’t you think the exception I posted above would be avoided?

Again: My plug-in (it’s an RCP app) runs fine now matter how many times I run it from within MyEclipse (Run, Debug). Once I use the DBE though, the only way I can recover is by shutting MyEclipse down and restarting it.

Here is the driver that MyEclipse uses:

<!--
MyEclipse Database Explorer Driver Repository
-->

<Beans version="1.0">
    <Bean Class="net.sourceforge.squirrel_sql.fw.sql.SQLDriver">
        <driverClassName>org.apache.derby.jdbc.EmbeddedDriver</driverClassName>
        <identifier Class="net.sourceforge.squirrel_sql.fw.id.UidIdentifier">
            <string>20543c5a:11638b689c3:-7ee0</string>
        </identifier>
        <jarFileName/>
        <jarFileNames Indexed="true">
            <Bean Class="net.sourceforge.squirrel_sql.fw.util.beanwrapper.StringWrapper">
                <string>C:\temp\db-derby-10.3.1.4-lib\db-derby-10.3.1.4-lib\lib\derby.jar</string>
            </Bean>
        </jarFileNames>
        <name>MyEclipseDriverName012</name>
        <url>jdbc:derby:homeword;create=true</url>
    </Bean>
    <Bean Class="com.genuitec.eclipse.sqlexplorer.utils.ConnectionProfile">
        <activate>false</activate>
        <driverIdentifier Class="net.sourceforge.squirrel_sql.fw.id.UidIdentifier">
            <string>20543c5a:11638b689c3:-7ee0</string>
        </driverIdentifier>
        <identifier Class="net.sourceforge.squirrel_sql.fw.id.UidIdentifier">
            <string>-2ecad9dd:116176ede2d:-7f93</string>
        </identifier>
        <name>HomewordDerby</name>
        <password encryption="true">Dws6fKz0xxVc2yJVjw4IiQ==</password>
        <promptForPassword>false</promptForPassword>
        <schema Indexed="true">
            <Bean Class="net.sourceforge.squirrel_sql.fw.util.beanwrapper.StringWrapper">
                <string>APP</string>
            </Bean>
        </schema>
        <schemaDisplayPolicy>2</schemaDisplayPolicy>
        <url>jdbc:derby:homeword;create=true</url>
        <userName>Homeword</userName>
    </Bean>
</Beans>

Thanks, Frank