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 02:14:43 UTC
[jira] Updated: (DERBY-3285) derby.system.bootAll does not work
unless derby.system.home is explicitly set
[ 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.