Return-Path: 
 <commons-user-return-9957-apmail-jakarta-commons-user-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-commons-user-archive@www.apache.org
Received: (qmail 77614 invoked from network); 6 Dec 2004 13:49:18 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 6 Dec 2004 13:49:18 -0000
Received: (qmail 55754 invoked by uid 500); 6 Dec 2004 13:49:00 -0000
Delivered-To: apmail-jakarta-commons-user-archive@jakarta.apache.org
Received: (qmail 55701 invoked by uid 500); 6 Dec 2004 13:49:00 -0000
Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:commons-user-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:commons-user-subscribe@jakarta.apache.org>
List-Help: <mailto:commons-user-help@jakarta.apache.org>
List-Post: <mailto:commons-user@jakarta.apache.org>
List-Id: "Jakarta Commons Users List" <commons-user.jakarta.apache.org>
Reply-To: "Jakarta Commons Users List" <commons-user@jakarta.apache.org>
Delivered-To: mailing list commons-user@jakarta.apache.org
Received: (qmail 55682 invoked by uid 99); 6 Dec 2004 13:48:59 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Received: from atlmail2.turner.com (HELO smtpgw2.turner.com) (64.236.240.147)
  by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 06 Dec 2004 05:48:58 -0800
Received: from cnncimss03.turner.com (CNNCIMSS03.turner.com [10.188.169.203])
	by smtpgw2.turner.com (8.12.10/8.12.11) with ESMTP id iB6DmuiJ008276
	for <commons-user@jakarta.apache.org>; Mon, 6 Dec 2004 08:48:56 -0500 (EST)
Received: from cnncmx10.turner.com ([10.188.170.10]) by cnncimss03.turner.com
 with InterScan Messaging Security Suite; Mon, 06 Dec 2004 08:48:55 -0500
Received: by cnncmx10.turner.com with Internet Mail Service (5.5.2657.72)
	id <WYTJT3C9>; Mon, 6 Dec 2004 08:48:56 -0500
Message-ID: <B07FC0A9AD7E614BAE8F5C9D31ADCA690250BC95@TWDEX01.turner.com>
From: "Botelho, Mauro" <Mauro.Botelho@turner.com>
To: "'Jakarta Commons Users List'" <commons-user@jakarta.apache.org>
Subject: RE: DB Connection TimeOut
Date: Mon, 6 Dec 2004 08:49:07 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Irfan,

>From what I understand you are trying to connect to a database server that is down. This database server is down from start, right?

If that is the case, it might be an issue with TCP/IP time out, nothing really to do with DBCP. What database are you using? Could the JDBC driver have any special setting to change that timeout?

Mauro

-----Original Message-----
From: Mohammad Irfan [mailto:irfan199@gmail.com]
Sent: Monday, December 06, 2004 1:02 AM
To: commons-user@jakarta.apache.org
Subject: DB Connection TimeOut


Hello, my name is Irfan. I have a problem about dbcp connection. After
I acquire a data source when I use the getConnection method for a DB
server that down, it stalled for a long time. Especially in Linux
platform. I figured that the connection timeout depends on the system.
It use default system connection timeout.
The Question is, how to set the connection timeout so in every
platform I have the same connection timeout time. I've tried the
setLoginTimeout method for the datasource but it's useless. Infact, it
throws Unsuported Operation exception.
Thank you for the answer.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org