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] Commented: (DERBY-232) Open Invitation to add a Question and Answer to Derby FAQs
Date Tue, 14 Jun 2005 19:40:12 GMT
    [ http://issues.apache.org/jira/browse/DERBY-232?page=comments#action_12313635 ] 

Sunitha Kambhampati commented on DERBY-232:

Q. I get a lock timeout error, how do I debug this ? 
To debug lock timeout errors, set derby.locks.monitor=true and derby.locks.deadlockTrace=true
in derby.properties , 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.

This should probably go in section - using derby.. 

> Open Invitation to add a Question and Answer to Derby FAQs
> ----------------------------------------------------------
>          Key: DERBY-232
>          URL: http://issues.apache.org/jira/browse/DERBY-232
>      Project: Derby
>         Type: Task
>   Components: Web Site
>     Reporter: Jean T. Anderson
>     Assignee: Jean T. Anderson
>     Priority: Trivial

> Add a comment to this Jira issue with the FAQ entry (both the question and the answer)
you would like to be added to http://incubator.apache.org/derby/faq.html, and the assignee
will add it.
> Indicate in your comment if the FAQ belongs in the "Developing Derby" or "Using Derby"

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message