Derby
  1. Derby
  2. DERBY-3285

Make derby.system.bootAll work regardless of whether derby.system.home is explicitly set or not

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 10.3.1.4, 10.3.2.1, 10.4.1.3
    • Fix Version/s: None
    • Component/s: Services
    • Labels:
      None

      Description

      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.

        Activity

          People

          • Assignee:
            Unassigned
            Reporter:
            Dag H. Wanvik
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Development