Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-1762

Setting the derby.locks.waitTimeout as a system property using System.setProperty does not affect booted databases

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Invalid
    • Affects Version/s: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.3.1.4
    • Fix Version/s: None
    • Component/s: Documentation, Services
    • Labels:
      None

      Description

      Tuning guide for derby.locks.waitTimeout states it is a dynamic property, but when set as a system property using System.setProperty it does not change the timeout for any databases already booted. It might change it for databases that are booted after the change, I didn't test that.

      If the property is set as a database property then it is dynamic, taking effect immediately.

      Guess it affects all versions.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                djd Daniel John Debrunner
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: