[#DERBY-170] Inserting large string value into non-existent table causes communication link failure over Network Server.

Derby

Inserting large string value into non-existent table causes communication link failure over Network Server.

Created: 10/Mar/05 02:14 AM Updated: 24/May/06 04:01 AM

Return to search

Component/s:

Network Server

Affects Version/s:

None

Fix Version/s:

10.1.3.1, 10.2.1.6

Time Tracking:

Issue & Sub-Tasks

Issue Only

Not Specified

File Attachments:

File Name	Date Attached	Attached By	Size
assert_repro.java	2005-03-10 02:17 AM	A B	1 kB
changes.html	2006-01-13 01:59 AM	Bryan Pendleton	9 kB
stored_proc_repro.java	2005-03-10 02:17 AM	A B	4 kB
storedProcs.java	2005-03-10 02:17 AM	A B	13 kB
svn_jan12_2006.status	2006-01-13 01:59 AM	Bryan Pendleton	0.4 kB
svn_jan14_2006.diff	2006-01-15 04:55 AM	Bryan Pendleton	6 kB

Environment:

Derby Network Server running with either JDBC or ODBC driver.

Resolution Date:

29/Apr/06 12:33 AM

Sub-Tasks:

All

Open

No sub-tasks match this view.

Description

« Hide

The following failure, along with the 2 sub-tasks created under this issue, are reproducible both from a JDBC client (JCC) and from an ODBC client (in this case, DB2 Runtime Client). I've grouped them all together because they all share the characteristic of "large data transfer", though the context in which the transfer occurs is different for each failure.

Failure: When trying to insert a large string value (ex. 1 million chars) into a non-existent table using a prepared statement, an ASSERT failure occurs on the Derby side (because data size < 0), which leads to connection closure and communication link failure. Note that the problem does NOT happen if the target table actually exists. Repro can be found in the "assert_repro.java" file attached to this bug.

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

No work has yet been logged on this issue.