archives.apache.org/mod_mbox/db-derby-user/200903.mbox/%3c20090330092451.GD26813@innovation.ch%3e">disabling locking (
continued), or at
gmane. Unfortunately, however, this does not seem to be sufficient: Derby may still lock other rows, as documented in
Scope of locks in Derbys's developer guide. When this happens, the wait for the lock will eventually time out and an exception will be thrown. However, I have not enountered this issue so far. But a related issue is present in 10.4 and earlier, namely
DERBY-2991; testing with 10.5 indicates this issue has been resolved. For these reasons a flag is provided to restrict the number of concurrent write-transactions to one, and the {@link #TransactionalStore(URI,BlobStore,String) three-argument-constructor} will set thissingle-writer flag to true for derby 10.4 and earlier.
@author Ronald Tschalär