Using Derby 10.5, and running in network server mode, we have encountered an issue where the lock_table contained locks, yet these locks are not being deleted; Even after the system sat idle overnight, the locks entries persisted in the lock_table the next morning, and caused the system to function improperly.
We are using the default values for lock and deadlock timeouts. Our application is using JPA and Optimistic Locking. What would cause the locks to NOT be cleared and/or released (even after a lengthy timeout period)? http://old.nabble.com/file/p34515902/derbylocks.png -- View this message in context: http://old.nabble.com/LOCK_TABLE-not-cleared-%28Derby-10.5%29-tp34515902p34515902.html Sent from the Apache Derby Users mailing list archive at Nabble.com.
