db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Golgoth 14 (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-3650) Derby + Hibernate JPA 3.2.1 problem on entity with Blob/Clob
Date Tue, 29 Apr 2008 07:35:56 GMT
Derby + Hibernate JPA 3.2.1 problem on entity with Blob/Clob

                 Key: DERBY-3650
                 URL: https://issues.apache.org/jira/browse/DERBY-3650
             Project: Derby
          Issue Type: Bug
          Components: Network Client
    Affects Versions:
         Environment: Mac OSX 10.4
JDK 1.5.0_13
Hibernate EntityManager 3.2.1

            Reporter: Golgoth 14


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.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message