[DERBY-2990] ResultSet.getBlob holds locks even with READ_UNCOMMITTED isolation level

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 10.1.3.1, 10.2.2.0, 10.3.1.4, 10.4.1.3
• Component/s: JDBC
• Assignee: Unassigned
• Reporter: Katherine Marsden
• Created: 02/Aug/07 23:54
• Updated: 25/Jul/08 18:14
• Resolved: 07/Jul/08 19:26

Description

ResultSet.getBlob() holds locks even when isolation level is set to TRANSACTION_READ_UNCOMMITTED. See attached repro

java GetBlobLocks
Exception in thread "main" ERROR 40XL1: A lock could not be obtained within the time requested
at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
at org.apache.derby.impl.services.locks.LockSet.lockObject(Unknown Source)
at org.apache.derby.impl.services.locks.SinglePool.lockAnObject(Unknown Source)
at org.apache.derby.impl.services.locks.SinglePool.lockObject(Unknown Source)
at org.apache.derby.impl.store.raw.xact.RowLocking3.lockRecordForWrite(Unknown Source)
at org.apache.derby.impl.store.access.conglomerate.OpenConglomerate.lockPositionForWrite(Unknown Source)
at org.apache.derby.impl.store.access.conglomerate.GenericConglomerateController.delete(Unknown Source)
at org.apache.derby.impl.sql.execute.RowChangerImpl.deleteRow(Unknown Source)
at org.apache.derby.impl.sql.execute.DeleteResultSet.collectAffectedRows(Unknown Source)
at org.apache.derby.impl.sql.execute.DeleteResultSet.open(Unknown Source)
at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedStatement.executeUpdate(Unknown Source)
at GetBlobLocks.testBlobLocks(GetBlobLocks.java:46)
at GetBlobLocks.main(GetBlobLocks.java:11)
[C:/kmarsden/repro/getblob] echo $WS

Issue Links

• relates to: DERBY-2892 Closing a resultset after retrieving a large > 32665 bytes value with Network Server does not release locks