[
https://issues.apache.org/jira/browse/DERBY-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-3650:
----------------------------------
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
was:
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
Summary: internal multiple references from different rows to a single
BLOB/CLOB stream leads to various errors when second reference used. (was:
Derby + Hibernate JPA 3.2.1 problem on entity with Blob/Clob)
Changing the problem description to reflect the research so far on the issue.
> internal multiple references from different rows to a single BLOB/CLOB stream
> leads to various errors when second reference used.
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3650
> URL: https://issues.apache.org/jira/browse/DERBY-3650
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.3.3.0, 10.4.1.3
> Environment: Mac OSX 10.4
> JDK 1.5.0_13
> Hibernate EntityManager 3.2.1
> Reporter: Golgoth 14
> Assignee: Mike Matrigali
> Attachments: derby-3650_tests_diff.txt, Derby3650EmbeddedRepro.java,
> Derby3650FullClientRepro.java, Derby3650FullRepro.java, Derby3650Repro.java,
> DerbyHibernateTest.zip, testdb.zip, traces_on_FormatIdStream_alloc.txt,
> UnionAll.java
>
>
> 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
