You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-commits@db.apache.org by jt...@apache.org on 2005/06/15 02:10:20 UTC
svn commit: r190670 - in /incubator/derby/site/trunk: build/site/faq.html
src/documentation/content/xdocs/faq.xml
Author: jta
Date: Tue Jun 14 17:10:20 2005
New Revision: 190670
URL: http://svn.apache.org/viewcvs?rev=190670&view=rev
Log:
DERBY-232 Added Sunitha Kambhampati's FAQ entry on how to debug lock timeouts.
Modified:
incubator/derby/site/trunk/build/site/faq.html
incubator/derby/site/trunk/src/documentation/content/xdocs/faq.xml
Modified: incubator/derby/site/trunk/build/site/faq.html
URL: http://svn.apache.org/viewcvs/incubator/derby/site/trunk/build/site/faq.html?rev=190670&r1=190669&r2=190670&view=diff
==============================================================================
--- incubator/derby/site/trunk/build/site/faq.html (original)
+++ incubator/derby/site/trunk/build/site/faq.html Tue Jun 14 17:10:20 2005
@@ -245,6 +245,11 @@
Why do I get the error 'schema does not exist'?
</a>
</li>
+<li>
+<a href="#debug_lock_timeout">3.4.
+ I get a lock timeout error. How do I debug this?
+ </a>
+</li>
</ul>
</li>
<li>
@@ -568,9 +573,38 @@
to create in a particular schema and no explicit CREATE SCHEMA was issued.
</p>
</div>
-<a name="N10107"></a><a name="users_client"></a>
+<a name="N10107"></a><a name="debug_lock_timeout"></a>
+<h4 class="faq">3.4.
+ I get a lock timeout error. How do I debug this?
+ </h4>
+<div align="right">
+<a href="#debug_lock_timeout-menu">^</a>
+</div>
+<div style="margin-left: 15px">
+<p>
+ To debug lock timeout errors, set
+ <span class="codefrag">derby.locks.monitor=true</span>
+ and <span class="codefrag">derby.locks.deadlockTrace=true</span> in
+ <span class="codefrag">derby.properties</span>.
+ This will print the lock table information to the derby.log
+ when the timeout happens.
+ If you also set
+ <span class="codefrag">derby.language.logStatementText=true</span>,
+ then all the statements executed on the system will be written
+ out to the <span class="codefrag">derby.log</span>.
+ Statement information also includes the transaction id on
+ which the statement is being executed.
+ You can use the transaction id
+ holding the lock in the lock table dump
+ to do a reverse search for the transaction id in
+ <span class="codefrag">derby.log</span>,
+ making it possible
+ to narrow down which statements may be holding the locks.
+ </p>
+</div>
+<a name="N10121"></a><a name="users_client"></a>
<h3 class="boxed">4. Using Derby: Client Programming</h3>
-<a name="N1010B"></a><a name="clientserv"></a>
+<a name="N10125"></a><a name="clientserv"></a>
<h4 class="faq">4.1.
Can you use Derby for client-server applications?
</h4>
@@ -591,7 +625,7 @@
<a href="papers/DerbyClientSpec.html">Derby Network Client</a>.
</p>
</div>
-<a name="N10123"></a><a name="netclient"></a>
+<a name="N1013D"></a><a name="netclient"></a>
<h4 class="faq">4.2.
Does Derby include a client-server ("network") jdbc driver?
</h4>
@@ -619,7 +653,7 @@
must not be used for production</a>.
</p>
</div>
-<a name="N1013A"></a><a name="db2_jcc_errors"></a>
+<a name="N10154"></a><a name="db2_jcc_errors"></a>
<h4 class="faq">4.3.
How can I get the message text for an error using the DB2 JDBC
Universal Driver?
@@ -637,7 +671,7 @@
mail list topic.
</p>
</div>
-<a name="N10149"></a><a name="derby_xa"></a>
+<a name="N10163"></a><a name="derby_xa"></a>
<h4 class="faq">4.4.
Can you execute a query that spans two Derby databases
across different JVMs?
@@ -663,7 +697,7 @@
used for production</a>.
</p>
</div>
-<a name="N10160"></a><a name="derby_faster"></a>
+<a name="N1017A"></a><a name="derby_faster"></a>
<h4 class="faq">4.5.
Are there any tips to make Derby go faster?
</h4>
Modified: incubator/derby/site/trunk/src/documentation/content/xdocs/faq.xml
URL: http://svn.apache.org/viewcvs/incubator/derby/site/trunk/src/documentation/content/xdocs/faq.xml?rev=190670&r1=190669&r2=190670&view=diff
==============================================================================
--- incubator/derby/site/trunk/src/documentation/content/xdocs/faq.xml (original)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/faq.xml Tue Jun 14 17:10:20 2005
@@ -293,6 +293,33 @@
</p>
</answer>
</faq>
+ <faq id="debug_lock_timeout">
+ <question>
+ I get a lock timeout error. How do I debug this?
+ </question>
+ <answer>
+ <p>
+ To debug lock timeout errors, set
+ <code>derby.locks.monitor=true</code>
+ and <code>derby.locks.deadlockTrace=true</code> in
+ <code>derby.properties</code>.
+ This will print the lock table information to the derby.log
+ when the timeout happens.
+ If you also set
+ <code>derby.language.logStatementText=true</code>,
+ then all the statements executed on the system will be written
+ out to the <code>derby.log</code>.
+ Statement information also includes the transaction id on
+ which the statement is being executed.
+ You can use the transaction id
+ holding the lock in the lock table dump
+ to do a reverse search for the transaction id in
+ <code>derby.log</code>,
+ making it possible
+ to narrow down which statements may be holding the locks.
+ </p>
+ </answer>
+ </faq>
</faqsection>
<faqsection id="users_client">
<title>Using Derby: Client Programming</title>