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