[DERBY-6245] PreparedStatement.setString fails in client server case when the String size is 10923 or larger and PreparedStatement updates more than one row

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 10.11.1.1
• Component/s: JDBC, Network Server
• Labels: derby_triage10_11
• Urgency: Normal
• Issue & fix info: Repro attached
• Assignee: Unassigned
• Reporter: Mamta A. Satoor
• Created: 04/Jun/13 06:22
• Updated: 20/Jun/13 20:04

Description

In DERBY-6214, the workaround of using PreparedStatement.setString instead of setObject works only for smaller Strings but it fails in client server case when updating two or more rows and using setString with very large string. A reproducible test case is attached to DERBY-6214. The exception thrown is
java.io.EOFException: Stream has already been read and end-of-file reached and cannot be re-used.

Issue Links

• relates to: DERBY-6214 PreparedStatement.setObject(int, Object, Types.CLOB) fail with DerbyNet
• relates to: DERBY-6237 PreparedStatement.execute() fails starting 10.2 when multiple rows are updated and PreparedStatement.setCharacterStream(int, Reader, int) is used