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 18:01:14 GMT

    [ 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.


Mime
View raw message