Return-Path: 
 <derby-commits-return-12217-apmail-db-derby-commits-archive=db.apache.org@db.apache.org>
Delivered-To: apmail-db-derby-commits-archive@www.apache.org
Received: (qmail 13264 invoked from network); 20 Nov 2009 17:56:54 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 20 Nov 2009 17:56:54 -0000
Received: (qmail 4698 invoked by uid 500); 20 Nov 2009 17:56:54 -0000
Delivered-To: apmail-db-derby-commits-archive@db.apache.org
Received: (qmail 4645 invoked by uid 500); 20 Nov 2009 17:56:53 -0000
Mailing-List: contact derby-commits-help@db.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:derby-commits-help@db.apache.org>
list-unsubscribe: <mailto:derby-commits-unsubscribe@db.apache.org>
List-Post: <mailto:derby-commits@db.apache.org>
Reply-To: "Derby Development" <derby-dev@db.apache.org>
List-Id: <derby-commits.db.apache.org>
Delivered-To: mailing list derby-commits@db.apache.org
Received: (qmail 4636 invoked by uid 99); 20 Nov 2009 17:56:53 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Nov 2009 17:56:53 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Nov 2009 17:56:51 +0000
Received: by eris.apache.org (Postfix, from userid 65534)
	id 70FF623888FD; Fri, 20 Nov 2009 17:56:30 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r882655 -
 /db/derby/docs/trunk/src/devguide/cdevconcepts50894.dita
Date: Fri, 20 Nov 2009 17:56:30 -0000
To: derby-commits@db.apache.org
From: bpendleton@apache.org
X-Mailer: svnmailer-1.0.8
Message-Id: <20091120175630.70FF623888FD@eris.apache.org>
X-Virus-Checked: Checked by ClamAV on apache.org

Author: bpendleton
Date: Fri Nov 20 17:56:29 2009
New Revision: 882655

URL: http://svn.apache.org/viewvc?rev=882655&view=rev
Log:
DERBY-2845: Improve devguide tips on debugging deadlocks

This change adds some additional content to the Development Guide page on
debugging deadlocks. The additional content provides more information
about how to use the SYSCS_DIAG.LOCK_TABLE diagnostic table, and also
points to detailed information available in the Derby wiki.


Modified:
    db/derby/docs/trunk/src/devguide/cdevconcepts50894.dita

Modified: db/derby/docs/trunk/src/devguide/cdevconcepts50894.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevconcepts50894.dita?rev=882655&r1=882654&r2=882655&view=diff
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevconcepts50894.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevconcepts50894.dita Fri Nov 20 17:56:29 2009
@@ -25,9 +25,37 @@
 <prolog></prolog>
 <conbody>
 <p><ph conref="../conrefs.dita#prod/productshortname"></ph> provides a class
-to help you in this situation, <i>org.apache.derby.diag.LockTable</i>. You
+    to help you in this situation, <i>org.apache.derby.diag.LockTable</i>.
+    Access to the <i>LockTable</i> information is provided via the
+    SYSCS_DIAG.LOCK_TABLE diagnostic table.</p>
+<p>The SYSCS_DIAG.LOCK_TABLE
+diagnostic table shows all of the locks that are currently held in the <ph
+    conref="../conrefs.dita#prod/productshortname"></ph> database. 
+You can reference the SYSCS_DIAG.LOCK_TABLE diagnostic table directly
+in a statement.</p>
+<p>For
+    example:<codeblock>SELECT * FROM SYSCS_DIAG.LOCK_TABLE</codeblock></p>
+<p>When
+the SYSCS_DIAG.LOCK_TABLE diagnostic table is referenced in a statement, a
+snapshot of the lock table is taken.
+</p><p>
+    For more information about how to use this table:
+    <ul>
+        <li>See "SYSCS_DIAG diagnostic tables and functions" in the
+            <cite><ph conref="../conrefs.dita#pub/citref"></ph></cite>.</li>
+        <li>See the <xref format="html"
+            href="http://db.apache.org/derby/javadoc/engine/org/apache/derby/diag/LockTable.html" scope="external">LockTable API documentation</xref>.
+        </li>
+    </ul>
+    You
 can also set the property <i>derby.locks.deadlockTrace</i> to dump additional
 information to the derby.log file about any deadlocks that occur on your system. 
 See the Tuning Guide for more information on this property. For information, see the <cite><ph conref="../conrefs.dita#pub/citadmin"></ph></cite>.</p>
+<p>Additional general information about diagnosing locking problems can be
+    found in the <ph conref="../conrefs.dita#prod/productshortname"></ph>
+    Wiki at <xref format="html"
+        href="http://wiki.apache.org/db-derby/LockDebugging" scope="external">
+        http://wiki.apache.org/db-derby/LockDebugging</xref>.
+</p>
 </conbody>
 </concept>