Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 46235 invoked from network); 16 Dec 2005 21:50:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 16 Dec 2005 21:50:01 -0000 Received: (qmail 48254 invoked by uid 500); 16 Dec 2005 21:49:59 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 48229 invoked by uid 500); 16 Dec 2005 21:49:59 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 48220 invoked by uid 99); 16 Dec 2005 21:49:59 -0000 X-ASF-Spam-Status: No, hits=1.3 required=10.0 tests=SPF_FAIL X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Dec 2005 13:49:57 -0800 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 887B5182 for ; Fri, 16 Dec 2005 22:49:36 +0100 (CET) Message-ID: <431294474.1134769776556.JavaMail.jira@ajax.apache.org> Date: Fri, 16 Dec 2005 22:49:36 +0100 (CET) From: "Bryan Pendleton (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-767) DRDA Protocol Exception: invalid value during CLSQRY when using db2jcc driver and batch queries In-Reply-To: <2012487902.1134695865520.JavaMail.jira@ajax.apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ 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