db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (DERBY-2828) derby.locks.deadlockTrace docs claim the property is meaningless without derby.locks.monitor=true
Date Wed, 10 Sep 2014 19:28:34 GMT

     [ https://issues.apache.org/jira/browse/DERBY-2828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kim Haase closed DERBY-2828.
----------------------------
    Resolution: Won't Fix

We don't generally document anything specific to the lib-debug release.

> 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.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
>            Reporter: John H. Embretsen
>            Priority: Trivial
>              Labels: derby_triage10_5_2
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message