[
https://issues.apache.org/jira/browse/DERBY-2828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508538
]
John H. Embretsen commented on DERBY-2828:
------------------------------------------
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 update to reflect this?
> 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.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.
