You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Julius Stroffek (JIRA)" <ji...@apache.org> on 2006/11/20 16:57:03 UTC

[jira] Commented: (DERBY-1595) Network server fails with DRDAProtocolException if a BLOB with size 2147483647 is streamed from client

    [ http://issues.apache.org/jira/browse/DERBY-1595?page=comments#action_12451347 ] 
            
Julius Stroffek commented on DERBY-1595:
----------------------------------------

I was able to reproduce this but when I decreased the size of LOB to 2GB-2, I got a different exception only on client:

java.sql.SQLException: A network protocol error was encountered and the connection has been terminated: the requested command encountered an unarchitected and implementation-specific condition for which there was no architected message
        at org.apache.derby.client.am.SQLExceptionFactory.getSQLException(SQLExceptionFactory.java:46)
        at org.apache.derby.client.am.SqlException.getSQLException(SqlException.java:345)
        at org.apache.derby.client.am.PreparedStatement.execute(PreparedStatement.java:1565)
        at com.sun.stroffek.Main.main(Main.java:45)
Caused by: org.apache.derby.client.am.DisconnectException: A network protocol error was encountered and the connection has been terminated: the requested command encountered an unarchitected and implementation-specific condition for which there was no architected message
        at org.apache.derby.client.net.NetConnectionReply.parseCMDCHKRM(NetConnectionReply.java:888)
        at org.apache.derby.client.net.NetStatementReply.parseExecuteError(NetStatementReply.java:661)
        at org.apache.derby.client.net.NetStatementReply.parseEXCSQLSTTreply(NetStatementReply.java:332)
        at org.apache.derby.client.net.NetStatementReply.readExecute(NetStatementReply.java:70)
        at org.apache.derby.client.net.StatementReply.readExecute(StatementReply.java:55)
        at org.apache.derby.client.net.NetPreparedStatement.readExecute_(NetPreparedStatement.java:183)
        at org.apache.derby.client.am.PreparedStatement.readExecute(PreparedStatement.java:1788)
        at org.apache.derby.client.am.PreparedStatement.flowExecute(PreparedStatement.java:2108)
        at org.apache.derby.client.am.PreparedStatement.executeX(PreparedStatement.java:1571)
        at org.apache.derby.client.am.PreparedStatement.execute(PreparedStatement.java:1556)
        ... 1 more

> Network server fails with DRDAProtocolException if a BLOB with size 2147483647 is streamed from client
> ------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1595
>                 URL: http://issues.apache.org/jira/browse/DERBY-1595
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Server
>    Affects Versions: 10.2.1.6
>            Reporter: Andreas Korneliussen
>         Assigned To: Julius Stroffek
>            Priority: Minor
>
> When executing a program which inserts a BLOB of size 2GB-1, the Network server fails with DRDAProtocolException.  This happens before it starts handling the actual LOB data:
> java org.apache.derby.drda.NetworkServerControl start
> Apache Derby Network Server - 10.2.0.4 alpha started and ready to accept connections on port 1527 at 2006-07-26 14:15:21.284 GMT
> Execution failed because of a Distributed Protocol Error:  DRDA_Proto_SYNTAXRM; CODPNT arg  = 0; Error Code Value = c
> org.apache.derby.impl.drda.DRDAProtocolException
>         at org.apache.derby.impl.drda.DRDAConnThread.throwSyntaxrm(DRDAConnThread.java:441)
>         at org.apache.derby.impl.drda.DDMReader.readLengthAndCodePoint(DDMReader.java:554)
>         at org.apache.derby.impl.drda.DDMReader.getCodePoint(DDMReader.java:617)
>         at org.apache.derby.impl.drda.DRDAConnThread.parseSQLDTA_work(DRDAConnThread.java:4072)
>         at org.apache.derby.impl.drda.DRDAConnThread.parseSQLDTA(DRDAConnThread.java:3928)
>         at org.apache.derby.impl.drda.DRDAConnThread.parseEXCSQLSTTobjects(DRDAConnThread.java:3806)
>         at org.apache.derby.impl.drda.DRDAConnThread.parseEXCSQLSTT(DRDAConnThread.java:3640)
>         at org.apache.derby.impl.drda.DRDAConnThread.processCommands(DRDAConnThread.java:928)
>         at org.apache.derby.impl.drda.DRDAConnThread.run(DRDAConnThread.java:254)
> null
> org.apache.derby.impl.drda.DRDAProtocolException
>         at org.apache.derby.impl.drda.DRDAConnThread.throwSyntaxrm(DRDAConnThread.java:441)
>         at org.apache.derby.impl.drda.DDMReader.readLengthAndCodePoint(DDMReader.java:554)
>         at org.apache.derby.impl.drda.DDMReader.getCodePoint(DDMReader.java:617)
>         at org.apache.derby.impl.drda.DRDAConnThread.parseSQLDTA_work(DRDAConnThread.java:4072)
>         at org.apache.derby.impl.drda.DRDAConnThread.parseSQLDTA(DRDAConnThread.java:3928)
>         at org.apache.derby.impl.drda.DRDAConnThread.parseEXCSQLSTTobjects(DRDAConnThread.java:3806)
>         at org.apache.derby.impl.drda.DRDAConnThread.parseEXCSQLSTT(DRDAConnThread.java:3640)
>         at org.apache.derby.impl.drda.DRDAConnThread.processCommands(DRDAConnThread.java:928)
>         at org.apache.derby.impl.drda.DRDAConnThread.run(DRDAConnThread.java:254)

-- 
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