Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 754E8DA49 for ; Mon, 11 Mar 2013 15:05:14 +0000 (UTC) Received: (qmail 83525 invoked by uid 500); 11 Mar 2013 15:05:14 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 83445 invoked by uid 500); 11 Mar 2013 15:05:14 -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 83209 invoked by uid 99); 11 Mar 2013 15:05:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Mar 2013 15:05:13 +0000 Date: Mon, 11 Mar 2013 15:05:12 +0000 (UTC) From: "Rick Hillegas (JIRA)" To: derby-dev@db.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (DERBY-6094) Derby ignores DriverManager.setLoginTimeout() MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-6094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-6094: --------------------------------- Attachment: derby-6094-03-aa-retryOnInterrupt.diff Attaching derby-6094-03-aa-retryOnInterrupt.diff. This patch applies Dag's suggested changes. I am running tests now. I also added a login timeout to the InterruptResilienceTest. That forces the new logic to be excercised. With the new logic, I have successfully run InterruptResilienceTest and LoginTimeoutTest on Mac OSX and on Linux on top of VirtualBox on top of Mac OSX. Touches the following files: M java/engine/org/apache/derby/jdbc/Driver20.java M java/testing/org/apache/derbyTesting/functionTests/tests/store/InterruptResilienceTest.java > Derby ignores DriverManager.setLoginTimeout() > --------------------------------------------- > > Key: DERBY-6094 > URL: https://issues.apache.org/jira/browse/DERBY-6094 > Project: Derby > Issue Type: Bug > Affects Versions: 10.10.0.0 > Reporter: Rick Hillegas > Attachments: derby-6094-01-ac-enforceDriverManagerLoginTimeout.diff, derby-6094-01-ad-enforceDriverManagerLoginTimeout.diff, derby-6094-01-ae-enforceDriverManagerLoginTimeout.diff, derby-6094-02-aa-createDBFirst.diff, derby-6094-03-aa-retryOnInterrupt.diff, Driver20.java, LoginTimeoutTest.java, LoginTimeoutTest.java, LoginTimeoutTest.java, LoginTimeoutTest.java > > > If you set a login timeout using the DriverManager, Derby ignores the setting. I will attach a test case which shows this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira