db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3285) derby.system.bootAll does not work unless derby.system.home is explicitly set
Date Mon, 06 Jul 2009 14:46:15 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727553#action_12727553

Kathey Marsden commented on DERBY-3285:

I am having some trouble getting derby.system.bootAll to work even with derby.system.home
set. First I created a couple of databases.
[C:/kmarsden/repro/derby-3285] java org.apache.derby.tools.ij
ij version 10.6
ij> run 'prep.sql';
ij> connect 'jdbc:derby:dba;create=true';
ij> connect 'jdbc:derby:dba;shutdown=true';
ERROR 08006: Database 'dba' shutdown.
ij> connect 'jdbc:derby:dbb;create=true';
ij(CONNECTION1)> connect 'jdbc:derby:dbb;shutdown=true';
ERROR 08006: Database 'dbb' shutdown.
ij(CONNECTION1)> quit;

I verified there were no lck files in these database directories.
Then I started ij with derby.system.home and derby.system.bootAll set and created a third

java -Dderby.system.home=C:/kmarsden/repro/derby-3285 -Dderby.sytem.bootAll org.apache.derby.tools.ij
ij> connect 'jdbc:derby:dbc;create=true';

I think this should have booted databases dba and dbb too, but I checked the database directories
(without exiting ij) and see a db.lck file only for dbc. dba and dbb have none.
Any ideas what I am doing wrong?

> derby.system.bootAll does not work unless derby.system.home is explicitly set
> -----------------------------------------------------------------------------
>                 Key: DERBY-3285
>                 URL: https://issues.apache.org/jira/browse/DERBY-3285
>             Project: Derby
>          Issue Type: Bug
>          Components: Services
>    Affects Versions:,,
>            Reporter: Dag H. Wanvik
>            Priority: Minor
> Cf discussion under DERBY-2182, which revealed that bootAll only works as intended (?!)
when derby.system.home. If 
> it has its default value, user.dir, no autoboot takes place.  
> We also saw an exception: The network server sets derby.system.home explicitly, unless
> -noSecurityManager is set, so in this case the auto-booting is not affected by this bug.

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

View raw message