Affects Version/s: 10.3.1.4, 10.3.2.1, 10.4.1.3
Fix Version/s: None
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.
|Field||Original Value||New Value|
|Affects Version/s||10.4.0.0 [ 12312540 ]|
|Summary||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|
|Issue Type||Bug [ 1 ]||Improvement [ 4 ]|
|Workflow||jira [ 12419466 ]||Default workflow, editable Closed status [ 12799491 ]|