Return-Path: 
 <tomcat-user-return-107744-apmail-jakarta-tomcat-user-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tomcat-user-archive@www.apache.org
Received: (qmail 42995 invoked from network); 16 Aug 2004 18:06:49 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 16 Aug 2004 18:06:49 -0000
Received: (qmail 28043 invoked by uid 500); 16 Aug 2004 18:06:19 -0000
Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org
Received: (qmail 28028 invoked by uid 500); 16 Aug 2004 18:06:19 -0000
Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:tomcat-user-subscribe@jakarta.apache.org>
List-Help: <mailto:tomcat-user-help@jakarta.apache.org>
List-Post: <mailto:tomcat-user@jakarta.apache.org>
List-Id: "Tomcat Users List" <tomcat-user.jakarta.apache.org>
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Delivered-To: mailing list tomcat-user@jakarta.apache.org
Received: (qmail 28014 invoked by uid 99); 16 Aug 2004 18:06:19 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=FORGED_RCVD_HELO
X-Spam-Check-By: apache.org
Received: from [66.111.4.30] (HELO frontend1.messagingengine.com)
 (66.111.4.30)
  by apache.org (qpsmtpd/0.27.1) with ESMTP; Mon, 16 Aug 2004 11:06:16 -0700
Received: from server2.messagingengine.com (server2.internal [10.202.2.133])
	by frontend1.messagingengine.com (Postfix) with ESMTP id 24D09C14A5E
	for <tomcat-user@jakarta.apache.org>; Mon, 16 Aug 2004 14:06:13 -0400 (EDT)
Received: by server2.messagingengine.com (Postfix, from userid 99)
	id 6EE01851C9; Mon, 16 Aug 2004 14:06:13 -0400 (EDT)
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
MIME-Version: 1.0
X-Mailer: MIME::Lite 1.4  (F2.72; T1.001; A1.62; B3.01; Q3.01)
Subject: DBCP connection pooling by default?
To: "Tomcat User" <tomcat-user@jakarta.apache.org>
Date: Mon, 16 Aug 2004 13:06:13 -0500
From: "Stephen Charles Huey" <stephenhuey@fastmail.fm>
X-Sasl-Enc: IaR1kBFmZukgY6fqKd1c7g 1092679573
Message-Id: <1092679573.12982.202434916@webmail.messagingengine.com>
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

The 8th post in this Javaranch.com thread suggests that Tomcat uses DBCP
connection pooling by default:
http://www.midrangeserver.com/mpo/mpo081502-story04.html

That feature to indicate connection leaks sounds intriguing.  I found
the following in our server.xml and am wondering if this means we are
definitely using this Commons DBCP:

- <!--  Define the top level container in our container hierarchy 
  --> 
- <Engine name="Standalone" defaultHost="localhost" debug="0">
- <DefaultContext crossContext="true">
  <Resource name="jdbc/myResource" auth="Container"
  type="javax.sql.DataSource" /> 
- <ResourceParams name="jdbc/myResource">
- <parameter>
  <name>factory</name> 
  <value>org.apache.commons.dbcp.BasicDataSourceFactory</value> 
  </parameter>

I think we are NOT using it because we have some Java classes that are
intended to handle connection pooling, and they look similar to some of
the textbook ones floating around online.  I'm just wondering if there
would be connection pooling in place with the above XML if we didn't
somehow override that with our own connection pooling classes.  One
other thing is that we currently have to use the JDBC-ODBC bridge, so I
don't know if that would have anything to do with it.  

Thanks,
Stephen

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