Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 85677 invoked from network); 14 Aug 2006 23:43:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 14 Aug 2006 23:43:08 -0000 Received: (qmail 35666 invoked by uid 500); 14 Aug 2006 23:43:07 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 35629 invoked by uid 500); 14 Aug 2006 23:43:07 -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 35620 invoked by uid 99); 14 Aug 2006 23:43:07 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Aug 2006 16:43:07 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Aug 2006 16:43:07 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 51D1D41001A for ; Mon, 14 Aug 2006 23:40:14 +0000 (GMT) Message-ID: <31453259.1155598814317.JavaMail.jira@brutus> Date: Mon, 14 Aug 2006 16:40:14 -0700 (PDT) From: "Deepa Remesh (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Updated: (DERBY-1692) Client driver does not use the query timeout value set using Statement.setQueryTimeout() for subsequent executions using the same statement object In-Reply-To: <26779116.1155597793822.JavaMail.jira@brutus> 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-1692?page=all ] Deepa Remesh updated DERBY-1692: -------------------------------- Attachment: TestQueryTimeout.java Attaching a repro 'TestQueryTimeout.java' based on jdbcapi/SetQueryTimeout test. Repro passes with embedded driver but fails with client driver. To run with embedded driver: run the command "java TestQueryTimeout" To run with client driver: Start network server and run "java TestQueryTimeout client" As shown by the repro, client driver does not use the query timeout value set for a statement for subsequent executions. This is the case for all the Statement.executeXXX methods. getQueryTimeout returns the correct value. So I am guessing the problem is in network server not using the query timeout set initially. As I am not sure where the problem is, I have put both Network Client and server as the component. > Client driver does not use the query timeout value set using Statement.setQueryTimeout() for subsequent executions using the same statement object > -------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: DERBY-1692 > URL: http://issues.apache.org/jira/browse/DERBY-1692 > Project: Derby > Issue Type: Bug > Components: Network Server, Network Client > Affects Versions: 10.2.0.0, 10.3.0.0 > Reporter: Deepa Remesh > Attachments: TestQueryTimeout.java > > > I will attach a repro with more details. -- 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