db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Closed: (DERBY-4531) Client setCharacterStream closes its Reader argument stream in finalizer
Date Tue, 15 Mar 2011 20:24:29 GMT

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

Kathey Marsden closed DERBY-4531.

    Resolution: Fixed

> 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
>            Assignee: Dag H. Wanvik
>            Priority: Minor
>              Labels: derby_backport_reject_10_6
>             Fix For:
>         Attachments: Repro.java, derby-4531-1a-test_workaround.diff, derby-4531.diff,
derby-4531b.diff, derby-4531b.stat
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message