Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 6446 invoked from network); 4 Aug 2009 14:49:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 4 Aug 2009 14:49:39 -0000 Received: (qmail 79457 invoked by uid 500); 4 Aug 2009 14:49:43 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 79404 invoked by uid 500); 4 Aug 2009 14:49:43 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 79396 invoked by uid 99); 4 Aug 2009 14:49:43 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Aug 2009 14:49:43 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of brett.wooldridge@gmail.com designates 209.85.210.185 as permitted sender) Received: from [209.85.210.185] (HELO mail-yx0-f185.google.com) (209.85.210.185) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Aug 2009 14:49:33 +0000 Received: by yxe15 with SMTP id 15so6648109yxe.5 for ; Tue, 04 Aug 2009 07:49:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=hvjiKULMQArYmABF75nToYG84ZItEJuCEHGcVjjDm2Y=; b=IJgNRa7RpCYuUUBMwjfasEVC5u82dfXDejzwevu99fkn9TXjPOyO/Z+mVZ+vmFpN49 flBl8vijVcUM2cJKRMOW7NSt0mwrU2Kn6xGReLzNSt63pdbmN746lGgBGdauinEbd23D 5WAuTJ6bXR6XKnBhOlj63Poc2vvkS2Xoi3SGk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=eIktGtvkA4V34GopxP/vcotDXMVXzcPObnVkSpGZtDeqbvj6mObIJfTLNFwQq/Yh4R 1tMeb83I9eqzwTxOfl1J+2jpFgymGurw+O+E8sDC+/2SwQgZiaMpQqZl3naEq5rcHN+E KKuKMdISzzHnxZb5T6tsi0k5MtZ1xLZpGzbcE= MIME-Version: 1.0 Received: by 10.150.189.2 with SMTP id m2mr13229671ybf.224.1249397349305; Tue, 04 Aug 2009 07:49:09 -0700 (PDT) In-Reply-To: <4A7823C3.9010000@Sun.COM> References: <71a64ba60907300015v56edee45w12218e6cec4c1a79@mail.gmail.com> <4A716984.1080107@Sun.COM> <71a64ba60907300315t66748b14re44a6c234411d37d@mail.gmail.com> <4A7196D7.7060005@sbcglobal.net> <71a64ba60907300557m13ad118apa0062eb038a1cbcf@mail.gmail.com> <4A73468D.3080806@sbcglobal.net> <71a64ba60908030247n48514fa2y9a3a7ff3b1194346@mail.gmail.com> <71a64ba60908040235pdc91badne0cda48fcebeedf1@mail.gmail.com> <4A7823C3.9010000@Sun.COM> Date: Tue, 4 Aug 2009 23:49:09 +0900 Message-ID: <71a64ba60908040749n6d5a53cdre0a4ee158988db5d@mail.gmail.com> Subject: Re: Derby 10.5.1.1 regression From: Brett Wooldridge To: Derby Discussion Content-Type: multipart/alternative; boundary=000e0cd6a982304f0c047051fdac X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd6a982304f0c047051fdac Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Kristan, I will try running with the embedded driver (not sure I can easily, but I think I can). Because I'm in Tokyo, I'm a bit out of sync time-wise with North America. It's midnight here (10:00am in Chicago). So, I'll try it when I get into work tomorrow. It'll probably be "tonight" for you, or the wee hours of the morning before I post results. Thanks for bearing with me on this (everyone). -Brett On Tue, Aug 4, 2009 at 9:04 PM, Kristian Waagan wrote: > Brett Wooldridge wrote: > >> Anyone have some suggestions for debugging direction? I hate the thought >> that I'm stuck on <10.5 forever. Any other environment details, logging >> options, etc? >> > > This may be a stupid question, but is it possible to run the application > using an EmbeddedXADataSource? > It is still not quite clear to me if there is a real DRDA protocol error, > or if the protocol error occurs due to a non-DRDA related bug / error on the > server. > > I don't really know where to start looking for problems; in the client > driver or in the Clob handling on the server side. > I would eliminate one or more factors; > - DRDA (by running with the embedded driver only) > - Clob streaming (insert NULLs, or provide values as strings instead of > streams for Clob columns?) > > Since I don't know the application, I don't know how hard it is to do any > of this. > As usual, providing a repro would help a lot, but that may be hard given > the number of software components involved... > > Another thing to try, would be to follow up on Dag's suggestion: > Do you see the bug when using Derby 10.4 [1]? > > > Regards, > -- > Kristian > > [1] http://db.apache.org/derby/releases/release-10.4.2.0.cgi > >> >> Thanks, >> Brett >> >> >> On Tue, Aug 4, 2009 at 12:35 AM, Dag H. Wanvik > Dag.Wanvik@sun.com>> wrote: >> >> >> Looks like the client sends an SQLSTT (0x2414) code point (starting an >> SQL statement to prepare) at a point where a new DRDA command is >> expected (processCommands). The SQLSTT code point is only allowed >> inside prepare (parsePRPSQLSTTobjects) or direct execution >> (parseEXECSQLIMMobjects) contexts. I have no idea why. >> >> >> >> > --000e0cd6a982304f0c047051fdac Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Kristan,

I will try running with the embedded driver (no= t sure I can easily, but I think I can). =A0Because I'm in Tokyo, I'= ;m a bit out of sync time-wise with North America. =A0It's midnight her= e (10:00am in Chicago). =A0So, I'll try it when I get into work tomorro= w. =A0It'll probably be "tonight" for you, or the wee hours o= f the morning before I post results.

Thanks for bearing with me on this (everyone).

-Brett

On Tue, Aug 4, 20= 09 at 9:04 PM, Kristian Waagan <Kristian.Waagan@sun.com> wrote:
Brett Wooldridge wrote:
Anyone have some suggestions for debugging direction? =A0I hate the thought= that I'm stuck on <10.5 forever. =A0Any other environment details, = logging options, etc?

This may be a stupid question, but is it possible to run the application us= ing an EmbeddedXADataSource?
It is still not quite clear to me if there is a real DRDA protocol error, o= r if the protocol error occurs due to a non-DRDA related bug / error on the= server.

I don't really know where to start looking for problems; in the client = driver or in the Clob handling on the server side.
I would eliminate one or more factors;
- DRDA (by running with the embedded driver only)
- Clob streaming (insert NULLs, or provide values as strings instead of str= eams for Clob columns?)

Since I don't know the application, I don't know how hard it is to = do any of this.
As usual, providing a repro would help a lot, but that may be hard given th= e number of software components involved...

Another thing to try, would be to follow up on Dag's suggestion:
Do you see the bug when using Derby 10.4 [1]?


Regards,
--
Kristian

[1] http://db.apache.org/derby/releases/release-10.4.2.0.cgi

Thanks,
Brett



On Tue, Aug 4, 2009 at 12:35 AM, Dag H. Wanvik <Dag.Wanvik@sun.com <mailto:Dag.Wanvik@sun.com>= > wrote:


=A0 =A0Looks like the client sends an SQLSTT (0x2414) code point (starting= an
=A0 =A0SQL statement to prepare) at a point where a new DRDA command is =A0 =A0expected (processCommands). The SQLSTT code point is only allowed =A0 =A0inside prepare (parsePRPSQLSTTobjects) or direct execution
=A0 =A0(parseEXECSQLIMMobjects) contexts. I have no idea why.





--000e0cd6a982304f0c047051fdac--