From derby-user-return-11364-apmail-db-derby-user-archive=db.apache.org@db.apache.org Tue Aug 04 09:36:05 2009
Return-Path: <derby-user-return-11364-apmail-db-derby-user-archive=db.apache.org@db.apache.org>
Delivered-To: apmail-db-derby-user-archive@www.apache.org
Received: (qmail 54631 invoked from network); 4 Aug 2009 09:36:05 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 4 Aug 2009 09:36:05 -0000
Received: (qmail 50309 invoked by uid 500); 4 Aug 2009 09:36:09 -0000
Delivered-To: apmail-db-derby-user-archive@db.apache.org
Received: (qmail 50237 invoked by uid 500); 4 Aug 2009 09:36:09 -0000
Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:derby-user-help@db.apache.org>
list-unsubscribe: <mailto:derby-user-unsubscribe@db.apache.org>
List-Post: <mailto:derby-user@db.apache.org>
List-Id: <derby-user.db.apache.org>
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Delivered-To: mailing list derby-user@db.apache.org
Received: (qmail 50229 invoked by uid 99); 4 Aug 2009 09:36:09 -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 09:36:09 +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.217.206 as permitted sender)
Received: from [209.85.217.206] (HELO mail-gx0-f206.google.com) (209.85.217.206)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Aug 2009 09:35:59 +0000
Received: by gxk2 with SMTP id 2so6425444gxk.7
        for <derby-user@db.apache.org>; Tue, 04 Aug 2009 02:35:39 -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=PyD49TKw7EoWH0HNWdp0S4jgm2Y76aqeZluVyHN7Lpo=;
        b=L91xQr5F/93Yh+oR9Ux0z538UhcskFwa9YMu3OukfHntZtkYfljBG6aj3lbvs2ym1p
         GZH2rlRIc0lhFED8aFrGAuz7K0ZpOPABLg0xgOeR5CDVNmiBZj7MH6Crh5/pyvsMdDHb
         qCFl0jy5h3fXYT2wACC39SGE5kQ89CWXRWFMI=
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=BQ3o6YNzrRHWFqMRF14bShzaNvthvE5tJQxd5lZqc90f5hpLApBQJS1PFTu0xNYsKS
         zvaF618xcKves8a+9iisfG9/93g22+jeFjrH6PIcZhnIpL9QSajaRkTD9yaxoiaD0vBV
         BkoWUdJrQ7kIDqXMv4uPOb2v+WxfnSXBkuFuU=
MIME-Version: 1.0
Received: by 10.150.124.13 with SMTP id w13mr12755710ybc.119.1249378538956; 
	Tue, 04 Aug 2009 02:35:38 -0700 (PDT)
In-Reply-To: <x1oxmy6gzz9f.fsf@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>
	 <x1oxmy6gzz9f.fsf@sun.com>
Date: Tue, 4 Aug 2009 18:35:38 +0900
Message-ID: <71a64ba60908040235pdc91badne0cda48fcebeedf1@mail.gmail.com>
Subject: Re: Derby 10.5.1.1 regression
From: Brett Wooldridge <brett.wooldridge@gmail.com>
To: Derby Discussion <derby-user@db.apache.org>
Content-Type: multipart/alternative; boundary=000e0cd3bf0601319204704d9c3a
X-Virus-Checked: Checked by ClamAV on apache.org

--000e0cd3bf0601319204704d9c3a
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

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?

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

--000e0cd3bf0601319204704d9c3a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Anyone have some suggestions for debugging direction?=A0 I hate the thought=
 that I&#39;m stuck on &lt;10.5 forever.=A0 Any other environment details, =
logging options, etc?<br><br>Thanks,<br>Brett<br><br><br><div class=3D"gmai=
l_quote">
On Tue, Aug 4, 2009 at 12:35 AM, Dag H. Wanvik <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:Dag.Wanvik@sun.com">Dag.Wanvik@sun.com</a>&gt;</span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204,=
 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Looks like the client sends an SQLSTT (0x2414) code point (starting an<br>
SQL statement to prepare) at a point where a new DRDA command is<br>
expected (processCommands). The SQLSTT code point is only allowed<br>
inside prepare (parsePRPSQLSTTobjects) or direct execution<br>
(parseEXECSQLIMMobjects) contexts. I have no idea why.<br>
<br>
<br>
</blockquote></div><br>

--000e0cd3bf0601319204704d9c3a--