db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <derby-...@db.apache.org>
Subject [jira] Resolved: (DERBY-491) Protocol exception when Network Server tries to return ~32K of data or greater in a result set for a Java stored procedure.
Date Sat, 29 Apr 2006 05:44:39 GMT
     [ http://issues.apache.org/jira/browse/DERBY-491?page=all ]
     
Bryan Pendleton resolved DERBY-491:
-----------------------------------

    Fix Version: 10.1.3.0
                 10.1.2.4
     Resolution: Fixed

Merged the change from the trunk back to the 10.1 branch. The merge was straightforward. I
verified that I could still reproduce the bug in 10.1, that the test demonstrated the bug,
and that the code change fixed it.

Committed to subversion as revision 398093:
svn.apache.org/viewcvs?rev=398093&view=rev

> Protocol exception when Network Server tries to return ~32K of data or greater in a result
set for a Java stored procedure.
> ---------------------------------------------------------------------------------------------------------------------------
>
>          Key: DERBY-491
>          URL: http://issues.apache.org/jira/browse/DERBY-491
>      Project: Derby
>         Type: Sub-task

>   Components: Network Server
>     Versions: 10.1.1.0, 10.2.0.0, 10.0.2.2
>  Environment: Derby Network Server running with either JDBC or ODBC driver.
>     Reporter: A B
>     Assignee: Bryan Pendleton
>      Fix For: 10.2.0.0, 10.1.3.0, 10.1.2.4
>  Attachments: changes.html, storedProcs.java, stored_proc_repro.java, svn_Jan_13_2006.status,
svn_Jan_13_3006.diff, svn_jan_24_2006.diff, svn_jan_26_2006.diff
>
> When Derby Network Server tries to return ~32K or greater data as part of the result
set for a stored procedure, a protocol exception occurs and causes deallocation of the connection.
Repro can be found in the "stored_proc_repro.java" file, which uses the stored procedure "BIG_COL"
declared in "storedProcs.java". Both files are attached to this bug.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message