Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 89174 invoked from network); 27 Apr 2006 20:18:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 27 Apr 2006 20:18:03 -0000 Received: (qmail 98239 invoked by uid 500); 27 Apr 2006 20:18:02 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 98209 invoked by uid 500); 27 Apr 2006 20:18:02 -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 98200 invoked by uid 99); 27 Apr 2006 20:18:02 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Apr 2006 13:18:02 -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; Thu, 27 Apr 2006 13:18:01 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 4DCCA41000F for ; Thu, 27 Apr 2006 20:17:38 +0000 (GMT) Message-ID: <26028826.1146169058316.JavaMail.jira@brutus> Date: Thu, 27 Apr 2006 20:17:38 +0000 (GMT+00:00) From: "Olav Sandstaa (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Updated: (DERBY-1090) Implement Connection.isValid as defined by JDBC4 In-Reply-To: <1632067244.1141853139141.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-1090?page=all ] Olav Sandstaa updated DERBY-1090: --------------------------------- Derby Info: [Patch Available] > Implement Connection.isValid as defined by JDBC4 > ------------------------------------------------ > > Key: DERBY-1090 > URL: http://issues.apache.org/jira/browse/DERBY-1090 > Project: Derby > Type: Sub-task > Components: JDBC > Reporter: Olav Sandstaa > Assignee: Olav Sandstaa > Priority: Minor > Fix For: 10.2.0.0 > Attachments: client1090_patch1.diff, client1090_patch2.diff, embedded1090-isclosed.diff, embedded1090-query.diff > > The Javadoc for JDBC4 says this about Connection.isValid: > boolean isValid(int timeout) throws SQLException > Returns true if the connection has not been closed and is still valid. The driver shall submit a query on the connection or use some other mechanism that positively verifies the connection is still valid when this method is called. > The query submitted by the driver to validate the connection shall be executed in the context of the current transaction. > Parameters: timeout - - The time in seconds to wait for the database operation used to validate the connection to complete. If the timeout period expires before the operation completes, this method returns false. A value of 0 indicates a timeout is not applied to the database operation. > Returns: true if the connection is valid, false otherwise -- 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