Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 36209 invoked from network); 14 Mar 2006 17:54:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 14 Mar 2006 17:54:11 -0000 Received: (qmail 78779 invoked by uid 500); 14 Mar 2006 17:54:10 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 78548 invoked by uid 500); 14 Mar 2006 17:54:09 -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 78539 invoked by uid 99); 14 Mar 2006 17:54:09 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Mar 2006 09:54:09 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [67.116.30.6] (HELO red.amberpoint.com) (67.116.30.6) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Mar 2006 09:54:09 -0800 Received: from [127.0.0.1] (bp-work.edgility.com [10.10.11.5]) by red.amberpoint.com (8.12.11/8.12.11) with ESMTP id k2EHrkev029015 for ; Tue, 14 Mar 2006 09:53:46 -0800 (PST) Message-ID: <44170328.9020405@amberpoint.com> Date: Tue, 14 Mar 2006 09:53:44 -0800 From: Bryan Pendleton User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: derby-dev@db.apache.org Subject: Re: [jira] Updated: (DERBY-1080) Connection reset when using security mechanism=EUSRIDPWD results in protocol error. References: <517522583.1142358224486.JavaMail.jira@ajax> In-Reply-To: <517522583.1142358224486.JavaMail.jira@ajax> Content-Type: text/plain; charset=UTF-8; format=flowed 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 > I will try to see if the problem reproduces without your 1080 fix. Hi Sunitha, Yes, the problem reproduces without your fix. The output files are a bit different, but the symptom is the same: the test mysteriously exits without producing all the required output, and no other messages are produced. I think in a way this is good news, because it indicates that your DERBY-1080 changes are not implicated in the problem. How should we proceed? thanks, bryan