[ http://issues.apache.org/jira/browse/DERBY-767?page=all ]
Bryan Pendleton updated DERBY-767:
----------------------------------
Attachment: repro.java
This is the program I used to reproduce the bug. At the start of the program
are two different sets of lines. One is for connecting with the db2jcc driver;
the other is for connecting with the Derby Network Client. By changing which
set of lines you use, you can get either the Distributed Protocol Exception
(db2jcc) or the Batch Update Exception (derbyclient).
> 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
