Return-Path: 
 <tomcat-user-return-54916-qmlist-jakarta-archive-tomcat-user=nagoya.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org
Received: (qmail 99294 invoked from network); 25 Feb 2003 15:27:35 -0000
Received: from exchange.sun.com (192.18.33.10)
  by daedalus.apache.org with SMTP; 25 Feb 2003 15:27:35 -0000
Received: (qmail 1460 invoked by uid 97); 25 Feb 2003 15:29:12 -0000
Delivered-To: qmlist-jakarta-archive-tomcat-user@nagoya.betaversion.org
Received: (qmail 1453 invoked from network); 25 Feb 2003 15:29:11 -0000
Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12)
  by nagoya.betaversion.org with SMTP; 25 Feb 2003 15:29:11 -0000
Received: (qmail 94273 invoked by uid 500); 25 Feb 2003 15:26:15 -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 94210 invoked from network); 25 Feb 2003 15:26:15 -0000
Received: from www.shareowner.com (HELO shareowner.com) (66.46.24.147)
  by daedalus.apache.org with SMTP; 25 Feb 2003 15:26:15 -0000
Received: from exchange.int.shareowner.com (gw.shareowner.com [66.46.24.163])
	by shareowner.com (8.11.6/8.11.6) with ESMTP id h1PF9Y425518
	for <tomcat-user@jakarta.apache.org>; Tue, 25 Feb 2003 10:09:34 -0500
Received: by exchange.int.shareowner.com with Internet Mail Service
 (5.5.2656.59)
	id <FR39N9DZ>; Tue, 25 Feb 2003 10:26:17 -0500
Message-ID: 
 <F85F120F1E46D711A0EF00104B95BB87014451@dictaphone-comp.int.shareowner.com>
From: pqin@shareowner.com
To: tomcat-user@jakarta.apache.org
Subject: RE: Connection Pooling
Date: Tue, 25 Feb 2003 10:26:11 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2DCE2.3A505CE0"
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

------_=_NextPart_001_01C2DCE2.3A505CE0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

This is a Tomcat JNDI implementation. I tried different solutions =
Tomcat,
Oracle connection caching and commons. Among them, Tomcat's is very =
simple.
commons-dbcp + pooling require more coding but have more flexibility of
course.

Regards,
=20
=20
PQ
=20
"This Guy Thinks He Knows Everything"
"This Guy Thinks He Knows What He Is Doing"

-----Original Message-----
From: Malcolm Green [mailto:Malcolm.Green@kcom.com]=20
Sent: February 25, 2003 5:36 AM
To: 'Tomcat Users List'
Subject: RE: Connection Pooling

I have DBCP connection pooling working as follows using Tomcat 4.1.12:

Under the <Context> element for your application (this can either be in =
the
server.xml file or a separate xml file in the webapps dir)  I have the
following config:

 	      <Resource name=3D"jdbc/XXXX" scope=3D"Shareable"
type=3D"javax.sql.DataSource"/>

	      <ResourceParams name=3D"jdbc/XXXX">
      		<parameter>
		      	<name>factory</name>
=09
<value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
		      </parameter>

		      <parameter>
				<name>maxActive</name>
				<value>100</value>
			</parameter>

		      <parameter>
				<name>maxIdle</name>
				<value>30000</value>
			</parameter>

		      <parameter>
				<name>maxWait</name>
				<value>100</value>
			</parameter>
       =20
		      <parameter>
				<name>username</name>
				<value>theUser</value>
			</parameter>
	=09
		      <parameter>
				<name>password</name>
				<value>thePassword</value>
			</parameter>
                 =20
		     <parameter>
			      <name>driverClassName</name>
=09
<value>com.microsoft.jdbc.sqlserver.SQLServerDriver</value>
		     </parameter>
           =20
		    <parameter>
		      <name>url</name>
=09
<value>jdbc:microsoft:sqlserver://hostname:port;databasename=3DmyDB</val=
ue>
		    </parameter>

		    <parameter>
		      <name>validationQuery</name>
		      <value>select getdate()</value>
		    </parameter>

	  </ResourceParams>

This is an MS SQL Server config, but to change the db just make sure =
that
the requried JDBC jar file is in the common/lib directory and then =
change
the necessary elements above e.g. driverClassName etc.

In my web.xml for my app I have the following:

  <resource-ref>
    <res-ref-name>jdbc/XXXX</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
  </resource-ref>

To use the pool I have the following code in a servlet:  (I have left =
out
the try/catch block etc.)

  Context ctx =3D new InitialContext();
  DataSource ds =3D (DataSource)ctx.lookup("java:comp/env/jdbc/XXXX");
  conn =3D ds.getConnection();
  ....

Hope this helps.

Malcolm

-----Original Message-----
From: Sebasti=C2=AAo Carlos Santos [mailto:scarlosantos@bol.com.br]
Sent: 21 February 2003 00:15
To: tomcat-user@jakarta.apache.org
Subject: Connection Pooling


Somebody has some experience or example in the=20
configuration and use of pool of connections with the=20
commons-dbcp. =20
I am a little lost and I don't know through where to=20
begin. =20
All information will be well arrival. =20
I thank the help in advance

=20
________________________________________________________________________=
__
E-mail Premium BOL
Antiv=EDrus, anti-spam e at=E9 100 MB de espa=E7o. Assine j=E1!
http://email.bol.com.br/



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

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

------_=_NextPart_001_01C2DCE2.3A505CE0--