Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 80680 invoked from network); 28 Sep 2005 14:35:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 28 Sep 2005 14:35:52 -0000 Received: (qmail 57932 invoked by uid 500); 28 Sep 2005 14:35:51 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 57897 invoked by uid 500); 28 Sep 2005 14:35:51 -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: "Derby Development" Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 57886 invoked by uid 99); 28 Sep 2005 14:35:51 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Sep 2005 07:35:51 -0700 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=NO_REAL_NAME X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [192.18.42.13] (HELO nwkea-mail-1.sun.com) (192.18.42.13) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Sep 2005 07:35:56 -0700 Received: from phys-epost-1 ([129.159.136.14]) by nwkea-mail-1.sun.com (8.12.10/8.12.9) with ESMTP id j8SEZS2B014975 for ; Wed, 28 Sep 2005 07:35:28 -0700 (PDT) Received: from conversion-daemon.epost-mail1.sweden.sun.com by epost-mail1.sweden.sun.com (iPlanet Messaging Server 5.2 HotFix 1.24 (built Dec 19 2003)) id <0INJ00M0175WHJ@epost-mail1.sweden.sun.com> (original mail from Oyvind.Bakksjo@Sun.COM) for derby-dev@db.apache.org; Wed, 28 Sep 2005 16:35:27 +0200 (MEST) Received: from [129.159.112.222] (atum22.Norway.Sun.COM [129.159.112.222]) by epost-mail1.sweden.sun.com (iPlanet Messaging Server 5.2 HotFix 1.24 (built Dec 19 2003)) with ESMTPA id <0INJ00NOE7730T@epost-mail1.sweden.sun.com> for derby-dev@db.apache.org; Wed, 28 Sep 2005 16:35:27 +0200 (MEST) Date: Wed, 28 Sep 2005 16:35:27 +0200 From: Oyvind.Bakksjo@Sun.COM Subject: Re: [jira] Updated: (DERBY-579) Query timeout set for one statement may affect other statements with the same SQL string In-reply-to: <4334A6D4.2080901@Sourcery.Org> To: Derby Development Message-id: <433AAA2F.1010809@sun.com> Organization: Sun Microsystems MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en, no, ru User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040618 References: <1216783041.1127225428457.JavaMail.jira@ajax.apache.org> <4333FF25.5080908@sun.com> <4334A6D4.2080901@Sourcery.Org> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Satheesh Bandaram wrote: > I am not exactly objecting :-) , but it would be nice to add a test > case to show the problem the fix is attempting to fix. I suspect the > original issue is easy to introduce, but hard to catch. > > While we are on this topic, I noticed SetQueryTimeoutTest test takes > around 30-40 minutes on my laptop. On one of our build machines, it > actually runs for longer than 2 hours when the test harness actually > kills the test. (causing the test to fail everytime) Though this is more > of our test machine problem (it is really sloooow), taking 30-40 minutes > for one functional test seems too long. Is there anyway the test can be > made to run faster? You realize that you are making conflicting requests, don't you? ;-) More tests in less time! I ran the test in 15 minutes, which is less than what you are experiencing, but I still think it is too much. I'll look into making the test run faster. The problem is that it's hard to tune the size of the tables so you're "guaranteed" that the fetching of some rows will take longer than the timeout value. I'll also look at adding a testcase for the bug that this patch addresses. -- Oyvind Bakksjo Sun Microsystems, Database Technology Group Trondheim, Norway http://weblogs.java.net/blog/bakksjo/