db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (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 Wed, 18 Jan 2006 19:32:43 GMT
    [ http://issues.apache.org/jira/browse/DERBY-491?page=comments#action_12363145 ] 

Kathey Marsden commented on DERBY-491:
--------------------------------------


The change looks good.  When you sync up,  it would be good to add some comments about the
changes to the code and include a reference to DERBY-491 and the changes.html here.

The changes.html wonderful and educational as always.      I have not really worked with this
low  level protocol code much  so it is great to have such a great tutorial included with
the patch. 

After reading and learning more about these issues. I really think your proposal to fill the
buffer with a known value in sane builds or if derby.drda.debug=true  would be very valuable.
 It would be interesting even to see how we do in the tests with this  turned on.


> 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
>  Attachments: changes.html, storedProcs.java, stored_proc_repro.java, svn_Jan_13_2006.status,
svn_Jan_13_3006.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