Uma,
Do you make a new pool for every request? That takes up a lot of resources.
Are you positive you are shutting down the pool and the connection when you
are done with them? Ideally, you setup your pool once, store it in serlet
or application context, then use that on instance to hand you off
On Wed, 19 Jan 2005 16:43:25 +0530, Kalluru Uma. Maheswar
<[EMAIL PROTECTED]> wrote:
> Hi,
> I am looking for an example using org.apache.commons.dbcp.BasicDataSource and
> more over, I cant use a .war file to deploy my app (there are some problems)
If I understand you right, you need to set up y
PROTECTED]
> Inviato: mercoledì 19 gennaio 2005 11.42
> A: Struts Users Mailing List
> Oggetto: Re: Connection Pool best practice
>
>
> Kalluru Uma. Maheswar wrote:
>
> >Hi,
> >
> >I am using org.apache.commons.dbcp.BasicDataSource to implement a
> >co
-
From: Pavel Kolesnikov [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 19, 2005 4:12 PM
To: Struts Users Mailing List
Subject: Re: Connection Pool best practice
On Wed, 19 Jan 2005 15:52:20 +0530, Kalluru Uma. Maheswar
<[EMAIL PROTECTED]> wrote:
> And in the classes where I need
On Wed, 19 Jan 2005 15:52:20 +0530, Kalluru Uma. Maheswar
<[EMAIL PROTECTED]> wrote:
> And in the classes where I need database connection, I am saying
>
> DBPool dbPool = new DBPool();
>
> dbPool.getDataSource();
>
> By doing this, my application is getting slower. Initially I configured
> db
Kalluru Uma. Maheswar wrote:
Hi,
I am using org.apache.commons.dbcp.BasicDataSource to implement a
connection pooling and this is my class.
If you're using Tomcat, you're better-off using JNDI Datasource:
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/jndi-datasource-examples-howto.html#Databas
6 matches
Mail list logo
