Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 50499 invoked from network); 14 Mar 2006 18:21:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 14 Mar 2006 18:21:33 -0000 Received: (qmail 17037 invoked by uid 500); 14 Mar 2006 18:21:33 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 16999 invoked by uid 500); 14 Mar 2006 18:21:32 -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 16990 invoked by uid 99); 14 Mar 2006 18:21:32 -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 10:21:32 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= 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; Tue, 14 Mar 2006 10:21:32 -0800 Received: from ajax (localhost.localdomain [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 5DD40D49FE for ; Tue, 14 Mar 2006 18:21:11 +0000 (GMT) Message-ID: <1886942795.1142360471381.JavaMail.jira@ajax> Date: Tue, 14 Mar 2006 18:21:11 +0000 (GMT) From: "Bryan Pendleton (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-1080) Connection reset when using security mechanism=EUSRIDPWD results in protocol error. In-Reply-To: <746244975.1141690649296.JavaMail.jira@ajax> 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-1080?page=comments#action_12370382 ] Bryan Pendleton commented on DERBY-1080: ---------------------------------------- Sunitha, can you help me understand the purpose of the Thread.sleep(5000) line in testSecMec.java? If I change that line from (5000) to (100), the problem becomes *much* more reproducible. Is there a possibility that, on my machine, some action is sometimes taking longer than 5 seconds to perform, and so the problem is related to that sleep() call returning "too soon"? In your environment, what happens if you change the Thread.sleep() call? thanks, bryan > Connection reset when using security mechanism=EUSRIDPWD results in protocol error. > ----------------------------------------------------------------------------------- > > Key: DERBY-1080 > URL: http://issues.apache.org/jira/browse/DERBY-1080 > Project: Derby > Type: Bug > Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.1.1, 10.1.1.2, 10.1.2.0, 10.1.2.1, 10.1.2.2 > Reporter: Sunitha Kambhampati > Assignee: Sunitha Kambhampati > Fix For: 10.2.0.0 > Attachments: DebugTest.diff.txt, Derby1080.diff.txt, Derby1080.stat.txt, derby-1080-testSecMec.tmp, derby1080.2.diff.txt, derby1080.2.stat.txt, derbyTesting.jar, premature_shutdown_derby.log, premature_shutdown_sysinfo.out, testSecMec.DerbyNet.shutdown.std.log_with_prints, testSecMec_with_prints.tmp > > if connection is reset, the security mechanism related information for EUSRIDPWD is not reset correctly and this leads to a protocol error. -- 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