We have an application that has started to use Derby and we are running into some lock timeouts.
When several threads are trying to acquire the same lock, how does Derby decide which thread to service the next time the lock becomes available? Is it using Java locks? Thread priority? Something else? Am I better off increasing the timeout? Re-trying? Pointers to documentation/code appreciated. Thanks! -- Al
