[DERBY-3098] LOB locks are not released after free().

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.2.2.0, 10.3.1.4
• Fix Version/s: 10.3.2.1, 10.4.1.3
• Component/s: Store
• Environment: Any
• Assignee: Oystein Grovlen
• Reporter: Oystein Grovlen
• Created: 03/Oct/07 07:41
• Updated: 02/May/13 02:29
• Resolved: 15/Oct/07 13:59

Description

When getBlob/getClob is called on the ResultSet, the current row is
locked if the JDBC driver does not cache the entire LOB value in
memory. This is done to prevent the Blob/Clob object from being
changed. Until now, this lock has been held to the end of the
transaction.

JDBC4 introduced free() methods for the Blob/Clob class. The locking
should be changed so that the locks is releases when the Blob/Clob
object is freed.

Issue Links

• is blocked by: DERBY-3107 On client, Clob.free() does not release locators.
• is depended upon by: DERBY-2892 Closing a resultset after retrieving a large > 32665 bytes value with Network Server does not release locks