db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunitha Kambhampati (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-360) Add doc info to print lock table for timeout errors
Date Tue, 14 Jun 2005 19:28:46 GMT
Add doc info  to print lock table for timeout errors
----------------------------------------------------

         Key: DERBY-360
         URL: http://issues.apache.org/jira/browse/DERBY-360
     Project: Derby
        Type: Bug
  Components: Documentation  
    Reporter: Sunitha Kambhampati
    Priority: Minor


In version 10.1 docs, 
1. Admin guide - http://incubator.apache.org/derby/docs/adminguide/cadminlockvti83889.html,
also a small section on timeouts should be added. 

To debug lock timeout errors, set derby.locks.monitor=true and derby.locks.deadlockTrace=true
this will print the lock table information to the derby.log when the timeout happens.  If
you also set the derby.language.logStatementText=true , then all the statement executed on
the system will be written out to the derby.log. Statement information also includes the transaction
id on which the statement is being executed.  Using the transaction id that is holding the
lock in the lock table dump if you do a reverse search for the transaction id in derby.log,
it is possible to narrow down which statements may be holding the locks. 


--------------
Here is an example of lock table dump in derby.log  on a lock timeout:
ERROR 40XL2: A lock could not be obtained within the time requested.  The lockTable dump is:
2005-06-14 18:39:15.788 GMT
XID       |TYPE         |MODE|LOCKCOUNT|LOCKNAME
--------------------------------------------------------------------------------------
*** The following row is the victim ***
146       |ROW          |S   |0        |(1,14)
*** The above row is the victim ***
139       |TABLE        |IX  |1        |Tablelock
146       |TABLE        |IS  |1        |Tablelock
139       |ROW          |X   |1        |(1,14)
--------------------------------------------------------------------------------------





-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message