![]()
![]() ![]() ![]() ![]() ![]() ![]() ![]() Documentation Top ![]() Global Index ![]() Reference Manual ![]() ![]() ![]() Developer's Guide ![]() ![]() Tuning Cloudscape ![]() ![]() |
cloudscape.locks.deadlockTraceFunctionCauses a stack trace of all threads involved in deadlocks (not just the victims) to be written to the error log (typically the cloudscape.LOG file). This property is meaningful only if the cloudscape.locks.monitor property is set to true. NOTE: This level of debugging is intrusive: it may alter the timing of the application, reduce performance severely, and produce a large error log file. It should be used with care. NEW: The cloudscape.locks.deadlockTrace property is new in Version 3.0. DefaultExampleScopedatabase-wide (publishable) Dynamic or StaticDynamic; the change takes effect immediately. For information about dynamic changes to properties, see Dynamic or Static Changes to Properties. | ||
![]() ![]() ![]() ![]() ![]() ![]() | ![]() ![]() Cloudscape Version 3.0 ![]() For technical support, go to: www.cloudscape.com and click Support. Copyright © 1998 and 1999 Cloudscape, Inc. All rights reserved. |