Do you still have the patches of Derby-666? They should come in handy. Am Samstag, 7. Juli 2007 schrieb Bryan Pendleton: > > all of these options - except the append - are already set, but there > > was no more information about this in the logs: > > DERBY-666 describes at least one case in which these properties > don't provide all the information that you might wish. > https://issues.apache.org/jira/browse/DERBY-666 > > For diagnosing my own application's locking behavior, I have found > SYSCS_DIAG.LOCK_TABLE (aka org.apache.derby.diag.LockTable) to > be extremely helpful: > http://db.apache.org/derby/docs/dev/ref/rrefsyscsdiagtables.html > > Here's another nice page on the LockTable VTI: > http://publib.boulder.ibm.com/infocenter/cldscp10/topic/com.ibm.cloudscape. >doc/hubprnt57.htm > > What I have done is to catch the lock timeout error, and in the catch > handling I have some code that dumps the lock table information to > a simple text file. By reading that file I have learned a lot about what > locks are being held. > > Also, depending on whether you are on Unix or Windows, it is useful to > combine this with using either "kill -QUIT" or "Control-Break" to get > a live stack trace of the threads in your application at the time of > the lock timeout. > > Hope this helps! > > thanks, > > bryan
-- Mit freundlichen Grüßen Kurt Huwig (Vorstand) Telefon 0681/96751-50, Telefax 0681/96751-66 http://www.iku-ag.de/ iKu Systemhaus AG, Am Römerkastell 4, 66121 Saarbrücken Amtsgericht: Saarbrücken, HRB 13240 Vorstand: Kurt Huwig, Andreas Niederländer Aufsichtsratsvorsitzender: Jan Bankstahl GnuPG 1024D/99DD9468 64B1 0C5B 82BC E16E 8940 EB6D 4C32 F908 99DD 9468
