Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id A1193200D50 for ; Mon, 4 Dec 2017 07:59:06 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 9FA88160C05; Mon, 4 Dec 2017 06:59:06 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id E684D160BF9 for ; Mon, 4 Dec 2017 07:59:05 +0100 (CET) Received: (qmail 92488 invoked by uid 500); 4 Dec 2017 06:59:05 -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 92478 invoked by uid 99); 4 Dec 2017 06:59:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Dec 2017 06:59:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 252011A0E14 for ; Mon, 4 Dec 2017 06:59:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 0onTPQz7Oqwz for ; Mon, 4 Dec 2017 06:59:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 4E0B660D85 for ; Mon, 4 Dec 2017 06:59:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 7812FE258B for ; Mon, 4 Dec 2017 06:59:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 8FCE0255CA for ; Mon, 4 Dec 2017 06:59:00 +0000 (UTC) Date: Mon, 4 Dec 2017 06:59:00 +0000 (UTC) From: "Mayur (JIRA)" To: derby-dev@db.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Issue Comment Deleted] (DERBY-6970) No support for setting connection timeout for a connection MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 04 Dec 2017 06:59:06 -0000 [ https://issues.apache.org/jira/browse/DERBY-6970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayur updated DERBY-6970: ------------------------- Comment: was deleted (was: Hi Bryan, We aren't getting any exceptions, our concern is just that when we are trying to set the connection time-out parameter to n number of seconds, it is taking 5 seconds by default for any parameter we assigned. We tried the following by using "derbyclient-10.13.1.1.jar" with client server mode communication like, ClientDataSource ds = new ClientDataSource(); ds.setLoginTimeout(15) / ds.setLoginTimeout(25) / ds.setLoginTimeout(2) and so on. So here as per the parameters connection time-out exception should have come after 15/25/2 seconds respectively. But for each and every parameter its taking 5 sec by default. Please help us out if you have any solution to the above issue. Its really affecting our performance request you to kindly respond quickly. Thank you Mayur ) > No support for setting connection timeout for a connection > ---------------------------------------------------------- > > Key: DERBY-6970 > URL: https://issues.apache.org/jira/browse/DERBY-6970 > Project: Derby > Issue Type: Improvement > Components: JDBC > Affects Versions: 10.13.1.1 > Environment: Linux Operating system Resin App server > Reporter: Satyabrata Mohanty > Attachments: DERBY_6970.java, DERBY_6970.java > > > https://stackoverflow.com/questions/44722659/providing-connection-time-out-in-derby-client-driver > This is the link where i have put the details of my requirement. Basically my question is, how we can provide a timeout to connection, if connection object not established within that specific time it must get out from infinite waiting and resulting any exception or null, but seems to be there is no such functionality in derby till now. Request you to kindly look-into this and provide your inputs like if there is a way to achieve this then mention it with clear steps or else if its not implemented then when we can get this must have required feature in derby. Its really affecting our performance request you to kindly respond quickly. > Thanks! -- This message was sent by Atlassian JIRA (v6.4.14#64029)