[DERBY-3650] internal multiple references from different rows to a single BLOB/CLOB stream leads to various errors when second reference used.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.3.3.0, 10.4.1.3, 10.5.3.0, 10.6.1.0
• Fix Version/s: 10.6.1.0
• Component/s: Network Client, SQL, Store
• Labels: derby_backport_reject_10_5
• Environment: Mac OSX 10.4; JDK 1.5.0_13; Hibernate EntityManager 3.2.1
• Urgency: Normal
• Issue & fix info: Known fix, Repro attached
• Bug behavior facts: Regression
• Assignee: Kristian Waagan
• Reporter: Golgoth 14
• Created: 29/Apr/08 07:35
• Updated: 17/Jun/13 09:19
• Resolved: 17/Feb/11 21:49

Description

Derby + Hibernate JPA 3.2.1 problem on entity with Blob/Clob

Hi,

I'm using Derby in Client - Server mode with Hibernate JPA EJB 3.0.
When a query on an entity containing a Clob and some joins on other entites is executed, an exception with the following message is thrown:
XJ073: The data in this BLOB or CLOB is no longer available. The BLOB/CLOB's transaction may be committed, or its connection is closed.

This problem occurs when the property "hibernate.max_fetch_depth" is greater than 0.
When hibernate.max_fetch_depth=0, the query works.

If Derby is configured in embedded mode, the query works independently of the value of hibernate.max_fetch_depth.

On the Hibernate's documentation, the advised value of hibernate.max_fetch_depth is 3.
Could you explain me if I made something wrong ?

Thank you.
Stephane

Issue Links

• is related to: DERBY-2111 EOFException when using stream as parameter for multi-row update statement in embedded driver
• is related to: DERBY-2892 Closing a resultset after retrieving a large > 32665 bytes value with Network Server does not release locks
• is related to: DERBY-4520 Refactor and extend data type cloning facilities