[DERBY-4531] Client setCharacterStream closes its Reader argument stream in finalizer

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.2.1.6, 10.2.2.0, 10.3.1.4, 10.3.2.1, 10.3.3.0, 10.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0, 10.6.1.0
• Fix Version/s: 10.7.1.1
• Component/s: Network Client
• Labels: derby_backport_reject_10_6
• Issue & fix info: Repro attached
• Bug behavior facts: Embedded/Client difference, Regression
• Assignee: Dag H. Wanvik
• Reporter: Dag H. Wanvik
• Created: 01/Feb/10 15:07
• Updated: 20/Feb/13 16:45
• Resolved: 15/Mar/11 20:23

Description

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.

Issue Links

• relates to: DERBY-6082 Investigate if openOnServer_ field in org.apache.derby.client.am.Statement is still needed.