You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Dag H. Wanvik (JIRA)" <ji...@apache.org> on 2007/12/18 00:27:43 UTC
[jira] Created: (DERBY-3285) derby.system.bootAll does not work
unless derby.system.home is explicitly set
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: 10.3.2.1, 10.3.1.4
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.
[jira] Commented: (DERBY-3285) derby.system.bootAll does not work
unless derby.system.home is explicitly set
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727650#action_12727650 ]
Kathey Marsden commented on DERBY-3285:
---------------------------------------
That was of course it. Thank you Dag. Next time I won't attempt triage before coffee.
I with the corrected command line I verified that that the databases boot when derby.system.home is set and don't if I do not set derby.system.home. I think though that this should be reclassified as an improvement since the doc is pretty specific that derby.system.bootAll applies only when derby.system.home is set.
http://db.apache.org/derby/docs/dev/tuning/rtunproperbootall.html
> 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: 10.3.1.4, 10.3.2.1, 10.4.1.3
> 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.
[jira] Commented: (DERBY-3285) derby.system.bootAll does not work
unless derby.system.home is explicitly set
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727636#action_12727636 ]
Dag H. Wanvik commented on DERBY-3285:
--------------------------------------
Kathey> java -Dderby.system.home=C:/kmarsden/repro/derby-3285 -Dderby.sytem.bootAll org.apache.derby.tools.ij
** typo: system
Could this be it?
Dag
Kathey> ij> connect 'jdbc:derby:dbc;create=true';
Kathey>
Kathey> 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.
Kathey> 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: 10.3.1.4, 10.3.2.1, 10.4.1.3
> 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.
[jira] Commented: (DERBY-3285) derby.system.bootAll does not work
unless derby.system.home is explicitly set
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ 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 database.
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: 10.3.1.4, 10.3.2.1, 10.4.1.3
> 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.
[jira] Updated: (DERBY-3285) Make derby.system.bootAll work
regardless of whether derby.system.home is explicitly set or not
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-3285:
---------------------------------
Issue Type: Improvement (was: Bug)
Summary: Make derby.system.bootAll work regardless of whether derby.system.home is explicitly set or not (was: derby.system.bootAll does not work unless derby.system.home is explicitly set)
> Make derby.system.bootAll work regardless of whether derby.system.home is explicitly set or not
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-3285
> URL: https://issues.apache.org/jira/browse/DERBY-3285
> Project: Derby
> Issue Type: Improvement
> Components: Services
> Affects Versions: 10.3.1.4, 10.3.2.1, 10.4.1.3
> 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.
[jira] Updated: (DERBY-3285) derby.system.bootAll does not work
unless derby.system.home is explicitly set
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-3285:
---------------------------------
Affects Version/s: 10.4.0.0
> 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: 10.3.1.4, 10.3.2.1, 10.4.0.0
> 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.