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 "Bryan Pendleton (JIRA)" <de...@db.apache.org> on 2005/12/16 22:49:36 UTC
[jira] Commented: (DERBY-767) DRDA Protocol Exception: invalid value during CLSQRY when using db2jcc driver and batch queries
[ http://issues.apache.org/jira/browse/DERBY-767?page=comments#action_12360630 ]
Bryan Pendleton commented on DERBY-767:
---------------------------------------
>From Kathey Marsden, on the mailing list:
> For DERBY-767, I think the protocol error is likely a JCC specific bug
> and not a DERBY Network Server bug as it does not reproduce with client.
> but I could be wrong. Usually, if I am not sure if a bug is JCC or
> NetworkServer, I will try JCC against DB2. If the case passes against
> DB2 with JCC , then I suspect a network server issue. If it still fails
> I blame JCC.
>
> Kathey
> DRDA Protocol Exception: invalid value during CLSQRY when using db2jcc driver and batch queries
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-767
> URL: http://issues.apache.org/jira/browse/DERBY-767
> Project: Derby
> Type: Bug
> Components: Network Server
> Versions: 10.0.2.0
> Environment: Reproduced on Windows XP using Sun JDK 1.4 and current trunk
> Reporter: Bryan Pendleton
> Priority: Minor
> Attachments: repro.java
>
> Distributed Protocol Error occurs when calling executeUpdate() after an addBatch()
> Kathey Marsden posted a snippet of code on the derby-dev mailing list, wondering if the problem still occurred with the current trunk. I tried her code with today's trunk, and sure enough I get a Distributed Protocol Exception, so I'm filing a bug.
> The attached test program has different symptoms depending on whether I run it with the db2jcc driver or with the Derby Network Client. With the db2jcc driver I get a Distributed Protocol Exception; with the Derby Network Client I get a Batch Update Exception.
> In the db2jcc configuration, the server gets:
> Server is ready to accept connections on port 1527.
> Execution failed because of a Distributed Protocol Error: DRDA_Proto_SYNTAXRM;
> CODPNT arg = 2113; Error Code Value = 14
> org.apache.derby.impl.drda.DRDAProtocolException
> at org.apache.derby.impl.drda.DRDAConnThread.throwSyntaxrm(DRDAConnThread.java:406)
> at org.apache.derby.impl.drda.DRDAConnThread.invalidValue(DRDAConnThread.java:6900)
> at org.apache.derby.impl.drda.DRDAConnThread.parseCLSQRY(DRDAConnThread.java:4895)
> at org.apache.derby.impl.drda.DRDAConnThread.processCommands(DRDAConnThread.java:792)
> at org.apache.derby.impl.drda.DRDAConnThread.run(DRDAConnThread.java:219)
> null
> org.apache.derby.impl.drda.DRDAProtocolException
> at org.apache.derby.impl.drda.DRDAConnThread.throwSyntaxrm(DRDAConnThread.java:406)
> at org.apache.derby.impl.drda.DRDAConnThread.invalidValue(DRDAConnThread.java:6900)
> at org.apache.derby.impl.drda.DRDAConnThread.parseCLSQRY(DRDAConnThread.java:4895)
> at org.apache.derby.impl.drda.DRDAConnThread.processCommands(DRDAConnThread.java:792)
> at org.apache.derby.impl.drda.DRDAConnThread.run(DRDAConnThread.java:219)
--
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