Derby
  1. Derby
  2. DERBY-2828

derby.locks.deadlockTrace docs claim the property is meaningless without derby.locks.monitor=true

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Trivial Trivial
    • Resolution: Unresolved
    • Affects Version/s: 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.2.2.0, 10.3.1.4
    • Fix Version/s: None
    • Component/s: Documentation
    • Urgency:
      Normal

      Description

      The documentation (Tuning Guide) for the derby.locks.deadlockTrace property says:

      "This property is meaningful only if the derby.locks.monitor property is set to true."

      http://db.apache.org/derby/docs/dev/tuning/rtunproper23835.html

      However, the property seems to be equally meaningful (prints lock cycles for deadlocks and lock lists for timeouts) regardless of whether derby.locks.monitor is set or not, or if set, regardless of whether it is set to true or false (with default settings for derby.stream.error.logSeverityLevel).

        Issue Links

          Activity

          Hide
          John H. Embretsen added a comment - - edited

          Seems like this is only an issue if the debug flag is true, e.g. for lib-debug distributions. The derby.locks.monitor property has an effect otherwise. Perhaps the docs should be updated to reflect this?

          Show
          John H. Embretsen added a comment - - edited Seems like this is only an issue if the debug flag is true, e.g. for lib-debug distributions. The derby.locks.monitor property has an effect otherwise. Perhaps the docs should be updated to reflect this?

            People

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

              Dates

              • Created:
                Updated:

                Development