From derby-dev-return-59775-apmail-db-derby-dev-archive=db.apache.org@db.apache.org Fri May 09 17:53:17 2008 Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 50701 invoked from network); 9 May 2008 17:53:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 May 2008 17:53:17 -0000 Received: (qmail 285 invoked by uid 500); 9 May 2008 17:53:18 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 255 invoked by uid 500); 9 May 2008 17:53:18 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 238 invoked by uid 99); 9 May 2008 17:53:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 May 2008 10:53:18 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 May 2008 17:52:41 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id B4BDE234C10C for ; Fri, 9 May 2008 10:52:55 -0700 (PDT) Message-ID: <1740519508.1210355575739.JavaMail.jira@brutus> Date: Fri, 9 May 2008 10:52:55 -0700 (PDT) From: "Kathey Marsden (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-3650) Derby + Hibernate JPA 3.2.1 problem on entity with Blob/Clob In-Reply-To: <196200967.1209454556080.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595680#action_12595680 ] Kathey Marsden commented on DERBY-3650: --------------------------------------- I am really quite stuck on this issue. Somehow we will need to defer the freeing of the lob until the result set is closed when it is used in a join if free or commit are called. I tried simply nulling out the InternalClob in EmbedClob and adding a finalize method to StoreStreamClob to close the stream, thinking that in this way we could perhaps rely on garbage collection to close the stream after it is no longer referenced, but even with a forced gc() after closing the result set, I saw failures in ClobTest.testLockingAfterFree, which indicates that there is still a reference to the stream until the end of the transaction. Perhaps this method would still work if I could figure out where the reference to the stream is and I could null that out too on free(). Then we could force a gc() on result set close. Perhaps I am off track all together. Does anyone know where else the stream is referenced or have any other ideas on this issue? Thanks Kathey > 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: 10.4.1.3 > Environment: Mac OSX 10.4 > JDK 1.5.0_13 > Hibernate EntityManager 3.2.1 > Reporter: Golgoth 14 > Attachments: Derby3650EmbeddedRepro.java, Derby3650FullRepro.java, Derby3650Repro.java, DerbyHibernateTest.zip, testdb.zip, traces_on_FormatIdStream_alloc.txt, UnionAll.java > > > 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.