When a foreign key constraint on a table is dropped, the associated statistics
row for the conglomerate is not removed
--
Key: DERBY-5681
URL:
indexStat daemon processing tables over an over even when there are no changes
in the tables
Key: DERBY-5680
URL: https://issues.apache.org/jira/browse/DERBY-5680
Code does different things depending if derby.locks.deadlockTrace=true is set
-
Key: DERBY-5564
URL: https://issues.apache.org/jira/browse/DERBY-5564
Project: Derby
An read-only XA transaction that has a timeout never has the timer canceled
when the transaction is complete
Key: DERBY-5562
URL:
Java deadlock between LogicalConnection40 and ClientXAConnection40
--
Key: DERBY-5560
URL: https://issues.apache.org/jira/browse/DERBY-5560
Project: Derby
Issue Type: Bug
Race conditions in LogicalConnection checking for a null physical connection
Key: DERBY-5561
URL: https://issues.apache.org/jira/browse/DERBY-5561
Project: Derby
Derby threads hanging when using ClientXADataSource and a deadlock or lock
timeout occurs
-
Key: DERBY-5552
URL: https://issues.apache.org/jira/browse/DERBY-5552
XA Transactions can becomes stuck if a connection from a XAResource without a
timeout terminates after performing work but before ending
Key: