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] Updated: (DERBY-4531) Client setCharacterStream closes its Reader argument stream in finalizer
Date Wed, 28 Apr 2010 12:47:32 GMT

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

Kristian Waagan updated DERBY-4531:

    Attachment: derby-4531-1a-test_workaround.diff

Attached patch 1a, which is a work-around for an intermittent test failure caused by the client
driver closing the stream in the finalizer.

Committed to trunk with revision 938972.
I plan to back-port this to the 10.6 branch.

> Client setCharacterStream closes its Reader argument stream in finalizer
> ------------------------------------------------------------------------
>                 Key: DERBY-4531
>                 URL: https://issues.apache.org/jira/browse/DERBY-4531
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Client
>    Affects Versions:,,,,,,,,,
>            Reporter: Dag H. Wanvik
>            Priority: Minor
>         Attachments: derby-4531-1a-test_workaround.diff, Repro.java
> The javadoc for PreparedStatement.setCharacterStream does not specify that the stream
passed in will be closed, only that it will read to the number of characters specified.
> For the embedded driver, the stream is not closed after execution; the client driver,
however, will close the stream when the internal stream object EncodedInputStream is garbage
collected, which can happen any time after the statement has been executed.
> I am not sure this a bug vs. the JDBC specification, but it would be nice to harmonize
client and embedded behavior on this.

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

View raw message