db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John H. Embretsen (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-2828) derby.locks.deadlockTrace docs claim the property is meaningless without derby.locks.monitor=true
Date Fri, 15 Jun 2007 12:34:26 GMT
derby.locks.deadlockTrace docs claim the property is meaningless without derby.locks.monitor=true
-------------------------------------------------------------------------------------------------

                 Key: DERBY-2828
                 URL: https://issues.apache.org/jira/browse/DERBY-2828
             Project: Derby
          Issue Type: Bug
          Components: Documentation
    Affects Versions: 10.2.2.0, 10.2.1.6, 10.1.3.1, 10.1.2.1, 10.1.1.0, 10.0.2.1, 10.3.0.0
            Reporter: John H. Embretsen
            Priority: Trivial


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).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message