db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-2734) LOB finalizers may close the underlying container while there are open streams
Date Tue, 25 May 2010 09:38:23 GMT

     [ https://issues.apache.org/jira/browse/DERBY-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Kristian Waagan resolved DERBY-2734.

    Fix Version/s:
       Resolution: Fixed

Resolving as fixed.
I think the issue got fixed as part of DERBY-2646 ("Cleanup of Clob control/support structures"),
where the finalizer was removed.

> LOB finalizers may close the underlying container while there are open streams
> ------------------------------------------------------------------------------
>                 Key: DERBY-2734
>                 URL: https://issues.apache.org/jira/browse/DERBY-2734
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, Store
>    Affects Versions:
>            Reporter: Knut Anders Hatlen
>            Priority: Minor
>             Fix For:
> Seen in the Tinderbox: http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/542818-org.apache.derbyTesting.functionTests.suites.All_diff.txt
> The code in LobStreamsTest that failed, looks like this:
>         InputStream lStream = rs3.getClob(1).getAsciiStream();
>         assertTrue("FAIL - Clob and file contents do not match",
>                 compareLob2File(fStream, lStream));
> I think the problem is that the Clob object is garbage collected before the stream has
been exhausted, and EmbedClob.finalize() closes the container. I think this affects earlier
releases as well, but I'm only marking it as a 10.3 issue for now since I haven't verified

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

View raw message