Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <287118538.1134070449094.JavaMail.jira@ajax.apache.org>
Date: Thu, 8 Dec 2005 20:34:09 +0100 (CET)
From: "Bryan Pendleton (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@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.
In-Reply-To: <521478780.1123182275791.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/DERBY-491?page=comments#action_12359759 ] 

Bryan Pendleton commented on DERBY-491:
---------------------------------------

This wasn't immediately clear from the stored_proc_repro.java file, but I seem to *also* get the same exception if I use the Derby Client Driver. I tweaked the reproduction code to say:

      Class.forName("org.apache.derby.jdbc.ClientDriver").newInstance();
      Connection conn = DriverManager.getConnection( "jdbc:derby://localhost:1527/testdb", "bah", "humbug");

instead of referencing the DB2JCC driver, and I get the following exception, which I assume is the same as the bug you observed:

 -=- ERROR 1 REPRODUCED:
org.apache.derby.client.am.DisconnectException: actual code point, -2 does not match expected code point, 8709
        at org.apache.derby.client.net.Reply.zThrowSyntaxError(Reply.java:1163)
        at org.apache.derby.client.net.Reply.parseLengthAndMatchCodePoint(Reply.java:1063)
        at org.apache.derby.client.net.NetStatementReply.parseOPNQRYRM(NetStatementReply.java:724)
        at org.apache.derby.client.net.NetStatementReply.parseResultSetCursor(NetStatementReply.java:400)
        at org.apache.derby.client.net.NetStatementReply.parseResultSetProcedure(NetStatementReply.java:377)
        at org.apache.derby.client.net.NetStatementReply.parseEXCSQLSTTreply(NetStatementReply.java:279)
        at org.apache.derby.client.net.NetStatementReply.readExecuteCall(NetStatementReply.java:97)
        at org.apache.derby.client.net.StatementReply.readExecuteCall(StatementReply.java:74)
        at org.apache.derby.client.net.NetStatement.readExecuteCall_(NetStatement.java:174)
        at org.apache.derby.client.am.Statement.readExecuteCall(Statement.java:1117)
        at org.apache.derby.client.am.PreparedStatement.flowExecute(PreparedStatement.java:1428)
        at org.apache.derby.client.am.CallableStatement.executeX(CallableStatement.java:124)
        at org.apache.derby.client.am.CallableStatement.execute(CallableStatement.java:114)
        at stored_proc_repro.main(stored_proc_repro.java:57)


> 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
>  Attachments: storedProcs.java, stored_proc_repro.java
>
> 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